-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CT-1785] [Bug] Update node_info
before LogModelResult
events
#6571
Comments
github-actions
bot
changed the title
[Bug]
[CT-1785] [Bug] Jan 11, 2023
node_info
not updated in NodeFinished
eventsnode_info
not updated in NodeFinished
events
6 tasks
jtcohen6
changed the title
[CT-1785] [Bug]
[CT-1785] [Bug] Jan 11, 2023
node_info
not updated in NodeFinished
eventsnode_info
not updated before LogModelResult
events
jtcohen6
changed the title
[CT-1785] [Bug]
[CT-1785] [Bug] Update Jan 11, 2023
node_info
not updated before LogModelResult
eventsnode_info
before LogModelResult
events
jtcohen6
added
enhancement
New feature or request
and removed
bug
Something isn't working
labels
Jan 11, 2023
Turns out this was me getting confused between |
jtcohen6
added
bug
Something isn't working
and removed
enhancement
New feature or request
labels
Jan 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
node_info
dictionary does not appropriately update for theNodeFinished
event.Running with the
1.4.latest
branch:I would expect the
CREATE VIEW
lines to include:node_finished_at
populatednode_status
=success
It looks like we have some legacy logic around this:
dbt-core/core/dbt/task/run.py
Lines 372 to 373 in eb200b4
dbt-core/core/dbt/task/runnable.py
Lines 233 to 241 in 7a61602
But we're not using the contextvars-based
get_node_info()
, introduced in #6325. I was able to get this working with a few small tweaks.While I was here:
HookFinished
is a weird name for this log line! It has nothing to do with hooks. Could we rename it to (e.g.)FinishedRunningStats
?The text was updated successfully, but these errors were encountered: