HIVE-28440: unblock hcatalog parquet project pushdown#5390
Merged
daijy merged 1 commit intoapache:masterfrom Aug 10, 2024
Merged
HIVE-28440: unblock hcatalog parquet project pushdown#5390daijy merged 1 commit intoapache:masterfrom
daijy merged 1 commit intoapache:masterfrom
Conversation
|
|
LGTM |
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
4 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?
to unblock hcatloader parquet table project pushdown. HCatLoader sets the needed columns intending to be used for project/filter pushdown, however, org.apache.hadoop.hive.ql.io.parquet.read.DataWritableReadSupport#init ReadContext skips project/filter pushdown when job properties 'columns' is not set. This change sets the 'columns' property.
Why are the changes needed?
to unblock hcatloader parquet table project pushdown
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
No
How was this patch tested?
tested locally