Skip to content
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

Lineage graph fails to render and due to "missing nodes" #2145

Open
kaupoondi opened this issue Apr 24, 2023 · 4 comments
Open

Lineage graph fails to render and due to "missing nodes" #2145

kaupoondi opened this issue Apr 24, 2023 · 4 comments
Labels
stale status:needs_triage For all issues that need to be processed type:bug An unexpected problem or unintended behavior

Comments

@kaupoondi
Copy link

kaupoondi commented Apr 24, 2023

Expected Behavior

We would expect that, with enough time to render, any complex lineage graph without cycles should render. For most of our tables, this seems to be the case.

Current Behavior

For some table (say table Y), we run into an issue where we get an error with the lineage rendering. The front-end is able to hit the metadata service and can fetch the entire lineage structure of Y as a JSON response. However, it seems that the D3 stratify algorithm fails to find a specific node (say table X) and errors. A good reference to the D3 algorithm can be found here.

The table X that it complains about does exist and we can go to its table page in the Amundsen front-end, view its metadata, and even view its lineage graph. However, this table X seems to be missing when table Y's lineage graph is trying to render.

Possible Solution

Steps to Reproduce

We looked through and reproduced this error for a few different tables via Selenium. The tables that the lineage render graph states were missing all exist in our Neo4j database.

Screenshots (if appropriate)

Below, we can see the error response that shows it fails to render due to a missing table.
Screen Shot 2023-04-24 at 4 26 49 PM

Context

For key tables, our users are not able to pull up the lineage graph and there are no useful errors to tell the end user that there is an issue either.

Your Environment

  • Amundsen version used: Frontend: frontend-4.2.0
  • Data warehouse stores: Snowflake
  • Deployment (k8s or native): k8s
  • Link to your fork or repository:
@kaupoondi kaupoondi added status:needs_triage For all issues that need to be processed type:bug An unexpected problem or unintended behavior labels Apr 24, 2023
@boring-cyborg
Copy link

boring-cyborg bot commented Apr 24, 2023

Thanks for opening your first issue here!

@stale
Copy link

stale bot commented May 20, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label May 20, 2023
@stale
Copy link

stale bot commented Jun 11, 2023

This issue has been automatically closed for inactivity. If you still wish to make these changes, please open a new pull request or reopen this one.

@stale stale bot closed this as completed Jun 11, 2023
@Golodhros Golodhros reopened this Jul 7, 2023
@stale stale bot removed the stale label Jul 7, 2023
@Golodhros Golodhros added stale and removed stale labels Jul 7, 2023
@stale
Copy link

stale bot commented Aug 7, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale status:needs_triage For all issues that need to be processed type:bug An unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants