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
I have searched the existing issues, and I could not find an existing issue for this bug
Which packages are affected?
dbt-adapters
dbt-tests-adapter
dbt-athena
dbt-athena-community
dbt-bigquery
dbt-postgres
dbt-redshift
dbt-snowflake
dbt-spark
Current Behavior
We upgraded our dbt to 1.9 version today. When we're running dbt snapshot with tags, one snapshot failure leading to all other snapshot failures.
On Snowflake query history, we're seeing this error - Your transaction was aborted. All statements will be ignored until you issue a COMMIT or a ROLLBACK.
Also, when we run single snapshot using select, it's running fine. But when we run with tag, it's failing
We have validated and make sure fail fast is false and there's no dependency between snapshots. Need some help here on understanding the actual root cause
Expected Behavior
Run rest of the models which are not dependent to the failing snapshot
Steps To Reproduce
1.Have a snapshot with duplicated records, which fails with Your transaction was aborted. All statements will be ignored until you issue a COMMIT or a ROLLBACK.
2. Have few snapshots running with the same tag as above snapshot
3. Run the dbt snapshot --select:
Is this a new bug?
Which packages are affected?
Current Behavior
We upgraded our dbt to 1.9 version today. When we're running dbt snapshot with tags, one snapshot failure leading to all other snapshot failures.
On Snowflake query history, we're seeing this error - Your transaction was aborted. All statements will be ignored until you issue a COMMIT or a ROLLBACK.
Also, when we run single snapshot using select, it's running fine. But when we run with tag, it's failing
We have validated and make sure fail fast is false and there's no dependency between snapshots. Need some help here on understanding the actual root cause
Expected Behavior
Run rest of the models which are not dependent to the failing snapshot
Steps To Reproduce
1.Have a snapshot with duplicated records, which fails with Your transaction was aborted. All statements will be ignored until you issue a COMMIT or a ROLLBACK.
2. Have few snapshots running with the same tag as above snapshot
3. Run the dbt snapshot --select:
Relevant log output
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: