-
Notifications
You must be signed in to change notification settings - Fork 4.8k
HIVE-29377: Fix inconsistency for partition filter LIKE clause #6240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
wecharyu
wants to merge
1
commit into
apache:master
Choose a base branch
from
wecharyu:HIVE-29377
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+97
−5
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The conversion rule for this PR is: if the character
.*is encountered in the partition predicate of Hive SQL, it is mapped to%in MySQL (matching zero or more characters), then the partition predicatea.*should be converted toa%in MySQL, and the direct SQL would query two partition entries, namelyabcandaf%.However, why is the query result from q.out empty here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The POSTHOOK Input shows that it got matching partitions from HMS, but hive optimizer
PartitionConditionRemoverwill filter partitions again by original pattern likea.*, and does not convert toa%so it will filter out the matching partitions.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So there is an issue here. The HMS can return partition information based on like
.*, but thePartitionConditionRemoverconsiders these partitions invalid. This seems inconsistent—we need to maintain consistency. cc @dengzhhu653 @deniskuzZAdditionally, I am not sure if
.*is a commonly used expression in SQL LIKE filtering. Could you give examples of similar LIKE matching usages in other sql engines?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SQL engines usually not use
.*as a filter, but HMS thrift APIs support it as a pattern, I think it's because HMS uses JDOmatches()for like filter.And Spark is using the
.*pattern for partition filter like here:https://github.com/apache/spark/blob/8cc2e4677d596bada67d05792f6fd896e5fc640f/sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveShim.scala#L827-L834
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
per my understanding, we don't have a single pattern for both jdo and the direct sql, jdo accepts
.*(Java-type pattern) for any sequences and the sql allows_%for the same game. When comes to HMS API, the user needs to take care of the pattern, whether it should be a Java-type pattern or sql pattern.Not sure why
PartitionConditionRemoverwould remove the partition condition, given the pruned partitions from Metastore is not empty.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can make a new topic on the difference in hive ql, maybe we can first fix the HMS inconsistency in JDO and Direct SQL here.