-
Notifications
You must be signed in to change notification settings - Fork 3k
HiveMetaHook implementation to enable CREATE TABLE and DROP TABLE from Hive queries #1495
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
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
c787816
HiveMetaHook implementation to enable CREATE TABLE and DROP TABLE fro…
fcd5406
Addressed review comments
734fc5d
Fix for partitionspec handling and tests for it
ffc108b
Store and remove TABLE_CREATION_FROM_HIVE property in HMS
f57c5a1
Fix checkstyle
2756a51
Handling external.table.purge
c0dcfb2
Reworked createTable from Hive
b9e88d5
Fixed drop table issue with HiveCatalog
274c72c
Removed unused imports
6aaaee4
Moved drop tables to the @After method
947620e
Enable hive engine for tests for storageHandler tests too
4847759
Enable hive engine for tables created by the Hook
0e26dd2
Cleaned up code after too many local fixes
4fd871d
Using the new metastore in tests
085ffb9
Revert to AlreadyExistsException for concurrent commits to the table
5ca165e
Reverted to create the HMS client anyway, since we use it to clean th…
f3bf7f3
Move to client-pool
1471f2a
Fixed Hive3 test failures
4296e45
Fixing rebase errors
2a50008
Else if formatting
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
Oops, something went wrong.
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.
Why is this needed? It may be nice to use this for applications, but for testing it seems like this allows us to pass the configuration incorrectly and still have tests pass. If it isn't needed, I'd rather remove it so that we must pass configuration properly.
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 Hive3 patch brought this in. If I understood @marton-bod correctly this was needed because in the HiveRunner there are some places where the config is not passed down, and this was the only way to fix the HMS client misery.
What I did here was only move this from the test class to the TestHiveMetastore class so it will affect the ClientPools as well
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.
That's correct. The rationale is outlined here: #1478 (comment)
As you mentioned, when using Hive3, not all threads spawned during
HiveRunnerinitialization receive our custom properties we set on theHiveShell, therefore using the system props is there to ensure they're picked up duringHiveConfconstruction. This is needed to get the tests working properly on Hive3, without thePersistenceManager-related flaky tests.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.
Okay, thanks for the reasoning. I guess I missed that this required a global setting in the other PR. I think this is fairly safe, since we always want to override the metastore URI using an option from the catalog's config.