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
github-actionsbot
changed the title
[Bug] node_info not updated in NodeFinished events
[CT-1785] [Bug] node_info not updated in NodeFinished events
Jan 11, 2023
jtcohen6
changed the title
[CT-1785] [Bug] node_info not updated in NodeFinished events
[CT-1785] [Bug] node_info not updated before LogModelResult events
Jan 11, 2023
jtcohen6
changed the title
[CT-1785] [Bug] node_info not updated before LogModelResult events
[CT-1785] [Bug] Update node_info before LogModelResult events
Jan 11, 2023
Turns out this was me getting confused between NodeFinished and LogModelResult! Less critical than I thought. Though I'm probably not the last person who will find this confusing, so still worth changing.
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: