Skip to content
Discussion options

You must be logged in to vote

Your diagnosis is right: it's a UI bug, and it isn't fixed yet. The lineage page has no entity fetcher for tableColumn, so it throws before sending any request.

At 2.0.7-release, handleEntitySelect navigates to /lineage/<hit entityType>/<fqn> for any hit. Then init() calls getEntityAPIfromSource(entityType)(decodedFqn) while building the Promise.allSettled array. That switch has no tableColumn case and no default, so it returns undefined. The call throws a TypeError, the permission call never starts, and showErrorToast gets a non-Axios error, so it shows the generic fallback. I ran a small Node mock of that flow: table made two requests, tableColumn made none and produced that toast.

The 2.0

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by Eleven-Hz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants