Closed john-jerome closed 2 years ago
Hey John - I think this should have been fixed by https://github.com/tailsdotcom/dbt_artifacts/pull/51. It hasn't been released yet, but could you try installing the latest commit to see if that fixes things?
packages.yml
- git: "https://github.com/tailsdotcom/dbt_artifacts.git"
I am also still having this problem, and I installed last week.
I am also still having this problem, and I installed last week.
Please could you provide a screenshot of the model and share which version of dbt_artifacts you have installed?
Hi @NiallRees
Thnx for getting back to me. Sure, please see below:
@GenDemo The latest version of the package is 0.6.0, could you give that a try?
Definitely - Today is my last day for the Christmas break, so it will be a while before I reply.
Cool, that seems to have worked! thnx :)
Hey there! We've been collecting dbt artifacts for a while now and already back when we started I noticed that the
fct_dbt__critical_path
table looked very suspicious (i.e. too good to be true) in our case, and it still does:I tried to investigate this issue by looking at the structure of the
fct_dbt__critical_path
model and it seems that everything untilsearch_path (node_ids, total_time)
produces the expected results (in particular, in our case). I was just confused by the fact thattotal_time
column seems to be a string instead of float. However, starting with the next CTE calledlongest_path_node_ids
we are getting the wrong node sequence. There must be something that thiscase when
does that I don't understand.Any help would be appreciated!