HIVE-29304: HS2 fails to start if cluster is configured with a mix of… #6166
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
… LDAP and Kerberos
|
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.
… LDAP and Kerberos
What changes were proposed in this pull request?
Enable to push JAAS configuration in case of hive.zookeeper.kerberos.enabled=true and hadoop.security.authentication=kerberos
Why are the changes needed?
If the Hadoop cluster is Kerberized, while HS2 is configured as only LDAP, the HS2 fails to start due to KillQueryZookeeperManager unable to connect to Zookeeper.
Does this PR introduce any user-facing change?
No
How was this patch tested?
HS2(LDAP) can start successfully after applying the dev jar