HIVE-29616: Fix incorrect column lineage when multiple subqueries with identical table aliases#6485
Open
ljq-dmr wants to merge 1 commit into
Open
HIVE-29616: Fix incorrect column lineage when multiple subqueries with identical table aliases#6485ljq-dmr wants to merge 1 commit into
ljq-dmr wants to merge 1 commit into
Conversation
…h identical table aliases
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changes were proposed in this pull request?
lineage column Predicate baseCols
Why are the changes needed?
The logic in ExprProcFactory#findSourceColumn resolves source columns from TopOps by matching table and field aliases. If a match is found, it returns the result directly. This implementation fails in scenarios involving multiple subqueries with identical table aliases (e.g., in a UNION statement). Because the search returns the first match it encounters, it may link to the wrong source column from a different subquery branch, leading to incorrect lineage
Does this PR introduce any user-facing change?
No
How was this patch tested?
mvn test -Pitests -pl itests/qtest -Dtest=TestMiniLlapLocalCliDriver -Dqfile=lineage8.q