Replies: 4 comments 2 replies
|
Good catch, and sorry for the confusion. What landed in v0.5 is the column-lineage engine - the resolver that traces every output column back through each stage to its root source columns (that's the foundation the changelog was referring to). The in-app viewer for it isn't wired up yet, which is exactly why you can't find it in the UI - that's on me for the changelog reading like it's already clickable. So today it's an engine/API capability, not a visible panel. A lineage view in the app is coming; I'll post here the moment it ships. Thanks for flagging it. |
|
Update: the in-app column lineage viewer is now shipped in v0.5.1. There is a Lineage button in the top bar (next to the Dives button) that opens a per-node view tracing each output column back to the source column(s) it derives from. Grab the fresh v0.5.1 binaries and you'll find it there. |
|
Ah amazing! I understand now, thank you! And I can see the output now :) is interactive viewer also on the roadmap e.g. similar to how it's implemented in SQLmesh? |
|
In 0.6.0 maybe! We will plan for it. |
|
Thank you, that sounds great! in the interim if the lineage table could be exportable /searchable it would be a great addition! |
|
Sure Adam. Will look into it. |
Uh oh!
There was an error while loading. Please reload this page.
Hello, I can see version 0.5 added column-level lineage per changelog. Where can I actually view it in the app itself, I am unable to find the functionality :) thank you
All reactions