We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have a project with some hooks: both on-run-start and on on-run-end. Whenever there are models to be run, the order is fine.
However when there no models to be run, the order may be incorrect. I see the on-run-end hooks running before (or paralel) with on-run-start hooks.
I would expect the on-run-end to start after on-run-start is done executing.
hook config:
on-run-start: - "{{ log('Run type: ' + flags.WHICH, info=True) }}" - "{{ log('Pre-hook: on-run-start', info=True) }}" on-run-end: - "{{ log('Post-hook: on-run-end', info=True) }}"
dbt build
dbt compile
tested against dbt-core 1.8.6 and dbt-core 1.9.2
12:14:47 Running with dbt=1.9.2 12:14:47 Registered adapter: duckdb=1.9.1 12:14:48 Found 1 model, 3 operations, 424 macros 12:14:48 12:14:48 Concurrency: 1 threads (target='dev') 12:14:48 12:14:48 Post-hook: on-run-end 12:14:48 Run type: compile 12:14:48 Pre-hook: on-run-start
- OS: Windows 11 24H2 - Python: 3.12.8 - dbt: 1.8.6 / 1.9.2
other (mention it in "Additional Context")
occurs with dbt-databricks and dbt-duckdb. assuming it is not relevant for this issue.
The text was updated successfully, but these errors were encountered:
Demo project available: https://github.com/frankivo/dbt_hooks_debug
Sorry, something went wrong.
This may be of interest to you: #4785
Thank you! I think I may have only searched open issues.
No branches or pull requests
Is this a new bug in dbt-core?
Current Behavior
I have a project with some hooks: both on-run-start and on on-run-end.
Whenever there are models to be run, the order is fine.
However when there no models to be run, the order may be incorrect.
I see the on-run-end hooks running before (or paralel) with on-run-start hooks.
Expected Behavior
I would expect the on-run-end to start after on-run-start is done executing.
Steps To Reproduce
hook config:
dbt build
and check logs (should be correct)dbt compile
and check logs (may be correct)tested against dbt-core 1.8.6 and dbt-core 1.9.2
Relevant log output
12:14:47 Running with dbt=1.9.2 12:14:47 Registered adapter: duckdb=1.9.1 12:14:48 Found 1 model, 3 operations, 424 macros 12:14:48 12:14:48 Concurrency: 1 threads (target='dev') 12:14:48 12:14:48 Post-hook: on-run-end 12:14:48 Run type: compile 12:14:48 Pre-hook: on-run-start
Environment
Which database adapter are you using with dbt?
other (mention it in "Additional Context")
Additional Context
occurs with dbt-databricks and dbt-duckdb. assuming it is not relevant for this issue.
The text was updated successfully, but these errors were encountered: