[DOP-23923] Add 'Column lineage' checkbox to LineageFilters #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dolfinus
force-pushed
the
feature/DOP-23923
branch
from
a7a099c to
e5c1be2
Compare
Zabilsya
approved these changes
Mar 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Depends on adding new query param to lineage API in MobileTeleSystems/data-rentgen#172.
With column lineage disabled (default):
With column lineage enabled:
DatasetNode height depends on number of fields in schema and if node has any column lineage. If column lineage is disabled or dataset columns are not related to any other dataset columns, then DatasetNode is compacted by default. User still may expand dataset schema, if required.