-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Support concurrent dbt runs #624
Comments
Hi @jakubro ! Thank you for opening this bug report. In examining this, there are multiple threads to dig into:
|
Thank you @amychen1776 for the explanation. Re 2) We've opened a ticket with AWS per your suggestion. Re 3) Do you by any chance have any guidance in documentation on how to structure jobs in DBT cloud? |
Awesome - thank you. And in terms of jobs, here is our communication on how to set up jobs (including how to chain jobs) https://docs.getdbt.com/docs/deploy/deploy-jobs#trigger-on-job-completion-- |
* remove boto3 peg * add changelog entry * remove boto3 refs in tests + mark skip flakey test --------- Co-authored-by: Mila Page <[email protected]>
As part of our repo clean up due to the consolidation of all dbt labs managed repos into one - I'm closing this issue out for now so we can have a broader conversation on dbt supporting concurrent runs at the dbt-core level. If you are still having issues with upgrading to |
Is this a new bug in dbt-redshift?
Current Behavior
We're observing a high failure rate after upgrading our DBT pipelines from version 1.5 to Versionless.
Our pipelines are failing with this error:
And the failing query is this:
My understanding of querying
information_schema
is that Redshift returns an error if a table is dropped while the query runs. And, DBT creates and drops some transient tables as it runs.It's important to note that we have 17 pipelines that run simultaneously. Most of them run every 10 minutes and some every 2 minutes.
Expected Behavior
DBT commands do not fail on quering
information_schema
.I would expect DBT to retry the query as it tries to build the catalog.
Steps To Reproduce
simple_model
Relevant log output
Attaching logs from the reproduction example from both terminals at the time of failure.
Logs from
dbt --debug run -s models/simple_model.sql
:Logs from
dbt --debug docs generate -s models/simple_model.sql
:Environment
Additional Context
pip freeze:
The text was updated successfully, but these errors were encountered: