Anyone here uses dagster-dbt and reads the output objects

DbtResult

and

NodeResult

? It seems like `NodeResult`’s

error

,

fail

,

skip

and

status

do not respond to whether the dbt node’s actual run result. Whether it failed, errored or succeeded, these values are all null. Can anyone confirm if this is a bug or not?

hi @Jonathan Mak! I can confirm that this is definitely a bug. However, we’re currently planning to significantly simplify the current JSON parsing -> Python class logic that exists in the library in favor of simply returning the parsed JSON dictionary, which would get rid of this bug (albeit in a kinda roundabout way). This is because the JSON schema of the dbt output can change from version to version, and we can’t really enforce what version of dbt you’re using with dagster-dbt, so weird parsing issues can sneak their way in if we’re too prescriptive on what we expect the run_results.json file to look like. Would this work for you?

This would work. My current workaround is just to call

parse_run_result

in a separate solid, somehow that works but I need to put in

project-dir

and

target-path

myself.