Hey, the

_tmp

tables of elementary seem to have been saved for more than six months back, which makes the describe tables action very long. is there a way to define retention or to delete them periodically?

Hi @Hen Ben-Hemo, thanks for reaching out! I am working on a fix for that as we speak 🙂 Can I ask if you disabled our on run ends by any chance? It will help me understand the issue better!

Hey @Idan Shavit no, I did not disabled your on run-end

Interesting 🤔 Care to share with me your dbt.log?

checking …

@Hen Ben-Hemo thank you for all the info 🙏 Which DWH are you using?

Databricks

I’m also interested in getting these tmp tables dropped. We are disabling on-run-end hooks in dev. I also posted in this today in support, but oddly I can only delete these tables if I wrap the names in quotes.

disable_tests_results: | # Override elementary default vars when running non-prod
      {%- if target.name == 'prod' and flags.WHICH not in ['generate'] -%} false
      {%- else -%} true
      {%- endif -%}
  disable_run_results: | # Override elementary default vars when running non-prod
      {%- if target.name == 'prod' and flags.WHICH not in ['generate'] -%} false
      {%- else -%} true
      {%- endif -%}
  disable_dbt_artifacts_autoupload: | # Override elementary default vars when running non-prod
      {%- if target.name == 'prod' and flags.WHICH not in ['generate'] -%} false
      {%- else -%} true
      {%- endif -%}
  disable_dbt_invocation_autoupload: | # Override elementary default vars when running non-prod
      {%- if target.name == 'prod' and flags.WHICH not in ['generate'] -%} false
      {%- else -%} true
      {%- endif -%}