fix(ui) Properly display column-level lineage with v2 field paths #6217
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes column-level lineage with v2 field paths to always use v1 field paths. This is necessary because
fineGrainedLineage
always produces v1 field paths whileschemaMetadata
on the entity uses v2 field paths. So we just need to be consistent here. So I always convert fields to v1 field paths when creating our source of truthcolumnsByUrn
.Checklist