HIVE-29622: Improve metastore direct-SQL partition lookup robustness#6509
Open
saihemanth-cloudera wants to merge 1 commit into
Open
HIVE-29622: Improve metastore direct-SQL partition lookup robustness#6509saihemanth-cloudera wants to merge 1 commit into
saihemanth-cloudera wants to merge 1 commit into
Conversation
|
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?
Direct-SQL partition name handling in the metastore was tightened. Partition lookups and related batch updates now use bound parameters instead of embedding names in SQL text.
Why are the changes needed?
Some partition-name inputs could be mishandled in direct-SQL paths, leading to incorrect partition resolution. This change makes name-based metastore operations more predictable and robust.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing test framework + Added a new test in TestObjectStore class