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
BIGTOP-3803: Fix Hive3.1.3 Metastore service compatible issue with Hadoop3.3.x when kerberos enabled #1001
Conversation
…doop3.3.x when kerberos enabled
- <curator.version>2.12.0</curator.version> | ||
+ <curator.version>4.2.0</curator.version> |
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 are specifying properties in do-component-build script to adjust versions of products. If just changing the curator.version
works, updating the do-component-build should be consistent. @timyuer.
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.
I will do it. Thanks. @iwasakims
Update as iwasakims comment. |
Hmm. I ran unit tests of Hive with
|
While I see NoSuchMethodError only in test classes (TestSlotZnode and TestZookeeperLockManager), it should be addressed as part of HIVE-26513. We can see if no defect by running tests again after it. |
The Hive community says it will not be fixed to be compatible with the Hadoop3.3.x, if using the Hadoop3.3.x, they recommend upgrading the Hive to the master branch. @iwasakims |
Then we should backport HIVE-22205 to Hive 3.1.3 as done for existing patch*.diff. We can not upgrade Hive before Hive 4.0.0 is released. @timyuer. |
|
Tested this PR with #1003.
+1 |
Merged. Thanks, @timyuer @iwasakims |
Fix Hive3.1.3 Metastore service compatible issue with Hadoop3.3.x when kerberos enabled
Description of PR
How was this patch tested?
For code changes: