You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, we use the dbt_artifacts package in our production environment, and we are wondering if there is a way to modify or adjust the logic for incremental models in terms of the query_id. Currently, it seems that for an incremental model, we only receive the latest query_id associated with the model (such as commit or alter when performing clustering). Is there a way for us to obtain the create or replace temporary table for <model_name>__dbt_temp, merge into, delete from, and/or other relevant queries?
The dbt-artifacts we use is version: 0.8.0, dbt version in dbt Cloud: 1.1
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, we use the
dbt_artifacts
package in our production environment, and we are wondering if there is a way to modify or adjust the logic for incremental models in terms of thequery_id
. Currently, it seems that for an incremental model, we only receive the latest query_id associated with the model (such as commit or alter when performing clustering). Is there a way for us to obtain the create or replace temporary table for <model_name>__dbt_temp, merge into, delete from, and/or other relevant queries?The
dbt-artifacts
we use is version: 0.8.0,dbt
version in dbt Cloud: 1.1Thank you in advance for your assistance.
Beta Was this translation helpful? Give feedback.
All reactions