Repository navigation
Lineage page: selecting a column search result shows "An unexpected error occurred." #37375
Environment
Steps
Expected: the lineage of the column's table opens, with the column selected (or column results are not offered in this search). Actual:
Comparison: selecting a table result works The URL becomes
So the entity lineage page seems to have no entity fetch for the Server side works for columns: Suggestion: when a Workaround: search for the table name instead, open the table's lineage, and turn on the column layer. |
Replies: 1 comment
|
Your diagnosis is right: it's a UI bug, and it isn't fixed yet. The lineage page has no entity fetcher for At The Either of these would be a small fix:
Until then, your workaround is the way to go: open the table and turn on the column layer. |
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,handleEntitySelectnavigates to/lineage/<hit entityType>/<fqn>for any hit. Theninit()callsgetEntityAPIfromSource(entityType)(decodedFqn)while building thePromise.allSettledarray. That switch has notableColumncase and no default, so it returnsundefined. The call throws a TypeError, the permission call never starts, andshowErrorToastgets a non-Axios error, so it shows the generic fallback. I ran a small Node mock of that flow:tablemade two requests,tableColumnmade none and produced that toast.The
2.0