Skip to content
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

HIVE-28676: Support custom partition patterns in MSCK repair table #5591

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

VenkatSNarayanan
Copy link
Contributor

Adds support for custom partitioning patterns to MSCK repair table.

What changes were proposed in this pull request?

Adds support for custom partitioning patterns to MSCK repair table.

Why are the changes needed?

HCatStorer supports custom partitioning patterns when using dynamic partitioning, but Hive itself does not support this. This change adds support for non-pathological cases to Hive.

Does this PR introduce any user-facing change?

MSCK repair table with a configured custom partition pattern would previously ignore that pattern and error on finding nonstandard paths. With the code from this PR, it will respect the defined custom pattern when it extracts partition key values from the paths.

Is the change a dependency upgrade?

No

How was this patch tested?

A test was added to TestHiveMetastoreChecker to test the common kinds of custom patterns supported.

Adds support for custom partitioning patterns to MSCK
repair table.
@zhangbutao
Copy link
Contributor

@VenkatSNarayanan
Copy link
Contributor Author

@VenkatSNarayanan Please check the failed tests. https://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-5591/2/tests. Thx

I can't seem to access that page, do I need to do something to see it?

@zhangbutao
Copy link
Contributor

hive-ci
@VenkatSNarayanan you can login in this page by your github account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants