Open sambloom92 opened 1 year ago
Thanks for reporting this @sambloom92 ! Just to get the context:
transaction_features_v1
? transaction_features_v2
or transaction_features
? (to understand if this is how it's really called in the database)Hi @Maayan-s,
For context this page from dbt gives a really good overview of the new versioning features, but to answer your questions:
Describe the bug dbt 1.5 introduced model versioning, however the elementary observability report does not display model versions in the lineage graph - each version appears as a separate node, but with the exact same name, so it does not accurately reflect the actual DAG. This diverges from dbt-core's lineage graph which does display the versions correctly.
To Reproduce Steps to reproduce the behavior:
dbt build
edr report
Expected behavior The lineage graph should display the model name with its version, as it is displayed in dbt core's docs.
Screenshots Below is an example of the dbt-core docs lineage graph, and the lineage graph in the elementary observability report:
Environment