-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CT-1385] [CT-1381] [Feature] Improved Lineage DAG Layout #330
Comments
thanks for opening @mkleinbort-ic! agree with improvements in this area in general, but it's likely not something we'll prioritize in the near future. going to transfer this to our |
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers. |
Since dbt best practices recommends this layering, it would be very useful to see it in the docs. I'd love to re-open this feature request. |
Is this your first time submitting a feature request?
Describe the feature
I propose 2 features:
Pinned x-coordinate ranges for nodes in the Dag
Minimized cross overs when deciding the y-coordinate of models.
In my view the x-coordinate would be the best way to view layers.
For example, consider a DAG with 4 layers:
I'd want no layer 1 node to be to the right of a layer 2 node, etc...
With regards to minimizing edge crossings. I know this is hard (NP Hard), but I think
dot
and similar tools do a pretty good job. See https://docs.google.com/viewer?url=http://www.graphviz.org/pdf/dotguide.pdfDescribe alternatives you've considered
I considered exporting the DAG file and visualizing it myself
Who will this benefit?
Anyone who uses the DAG as a form of troubleshooting/documentation
Are you interested in contributing this feature?
No, I don't know JS
Anything else?
No response
The text was updated successfully, but these errors were encountered: