This comes from a Tobiko Cloud customer. Good for tcloud DAG and/or vs code extension in lineage tab.
Feature suggestion:
We've had a few folks take stabs at trying to visualize our model DAGs in a more intuitive way. The UI visualizer's interactivity and column level lineage features are nice but the layout tends to become a bit of hard to parse when there are a more than a few models in the DAG. One of our attempts groups models by directory which IMO makes it a lot easier to parse the DAG at a high level before diving into a specific model.
For us specifically the directory structure works well with this kind of visualization but for a generic feature it would pigeonhole folks a little bit to organize their models in a way that works with the visualization. I think if there was an option to group models in the UI visualization by models' tags (or model properties in general, but tags would probably be enough for our use case) then we could get the best of both worlds. For example, for the included visualization we would have a grouping hierarchy of something like domain > product line > layer.
Tobiko only slack thread
This comes from a Tobiko Cloud customer. Good for tcloud DAG and/or vs code extension in lineage tab.
Feature suggestion:
We've had a few folks take stabs at trying to visualize our model DAGs in a more intuitive way. The UI visualizer's interactivity and column level lineage features are nice but the layout tends to become a bit of hard to parse when there are a more than a few models in the DAG. One of our attempts groups models by directory which IMO makes it a lot easier to parse the DAG at a high level before diving into a specific model.
For us specifically the directory structure works well with this kind of visualization but for a generic feature it would pigeonhole folks a little bit to organize their models in a way that works with the visualization. I think if there was an option to group models in the UI visualization by models' tags (or model properties in general, but tags would probably be enough for our use case) then we could get the best of both worlds. For example, for the included visualization we would have a grouping hierarchy of something like domain > product line > layer.
Tobiko only slack thread