amundsen
amundsen copied to clipboard
Bug Report - Lineage does not look good when there are lots of upstream and downstream
Lineage does not look good when there are lots of upstream and downstream
https://amundsenworkspace.slack.com/archives/C01A87A5EUU/p1627859139002600 https://amundsenworkspace.slack.com/archives/C01A87A5EUU/p1627859139002600
Expected Behavior
Current Behavior
Lineage shows cluttered view

Possible Solution
Steps to Reproduce
- Create lineage data with lots of tables (100+) either downstream or upstream
Screenshots (if appropriate)
Context
Your Environment
- Amunsen version used:
- Data warehouse stores:
- Deployment (k8s or native):
- Link to your fork or repository:
Thanks for opening your first issue here!
cc @danwom Have you tried the table list for lineage as well?
also cc @Golodhros
Table list works ok.
Hi Team, any updates on this
Hi @apalmercari we are aware of this - the lineage UI is pretty alpha. It's on our roadmap, but can't share a timeline just yet. In the meantime, I'd recommend using the list view. Thanks for filing the bug report.
@markgrover maybe you can give another update on this issue?
Hi @brunsgaard, no update. We did make an internal update to the UI at stemma.ai but haven't thought about contribution at the moment. We used React Flow for the new version but I am not sure if that's helpful to you.
Hi @markgrover, any plans on contributing React Flow implementation to the open-source? We are facing this issue as well and would be great to see it fixed!
No updates, unfortunately. My recommendation is to use the list view in the meantime. Patches greatly welcome here.
@markgrover Can you please share the documentation/link on how to enable "list view"? We were not aware of this option.
More details in this thread: https://amundsenworkspace.slack.com/archives/C01A87A5EUU/p1631302036018100
On Thu, 11 Aug 2022 at 12:54, Ozan Dogrultan @.***> wrote:
@markgrover https://github.com/markgrover Can you please share the documentation/link on how to enable "list view"? We were not aware of this option.
— Reply to this email directly, view it on GitHub https://github.com/amundsen-io/amundsen/issues/1443#issuecomment-1212425098, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANBLCZGAPJECSUVX2FVJWLVYVK6DANCNFSM5CEQ2ISA . You are receiving this because you were mentioned.Message ID: @.***>
@markgrover maybe better post the details here, since Amundsen's slack plan currently does not retain history for messages and files longer than 90 days.
Hi @Golodhros, this issue still remains open for us actually. Is there any plan to fix it in the near future?
Hi @Golodhros, this issue still remains open for us actually. Is there any plan to fix it in the near future?
Thanks for the heads up Ozan! We are changing the way of how we manage issues in Amundsen, so we'll close all that are already triaged to allow for voting on the most important.
I will release an announcement today in the channel about it.