nrg4878 opened a new pull request, #4691: URL: https://github.com/apache/hive/pull/4691
…ntegration (Naveen Gangam) <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, please read our contributor guidelines: https://cwiki.apache.org/confluence/display/Hive/HowToContribute 2. Ensure that you have created an issue on the Hive project JIRA: https://issues.apache.org/jira/projects/HIVE/summary 3. Ensure you have added or run the appropriate tests for your PR: 4. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP]HIVE-XXXXX: Your PR title ...'. 5. Be sure to keep the PR description updated to reflect all changes. 6. Please write your PR title to summarize what this PR proposes. 7. If possible, provide a concise example to reproduce the issue for a faster review. --> ### What changes were proposed in this pull request? We have various points in the hive codebase that communicate with zookeeper service. Apache Hive JDBC Driver fetches the HS2 URLs for service discovery. Hive Server2 uses ZK to register itself for service discovery, table locking, ZK TokenStore etc. Hive Metastore also uses ZK to register itself for service discovery, ZK Tokenstore If Zookeeper is TLS enabled with a different keystore/truststore type, we need to be able to specify this type when establishing this connection. Otherwise, it defaults to JKS which may not be the case all the time. ### Why are the changes needed? To be able to support service discovery (and other features) that use zookeeper in hive, we have to allow for a keystore/truststore type to be specified in the config. ### Does this PR introduce _any_ user-facing change? No, its backward compatible. But only in cases where non-JKS storetypes are used, we will need additional configuration either in the JDBC URL or in the hive-site.xml for HS2/HMS services. ### Is the change a dependency upgrade? No ### How was this patch tested? UTs -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org For additional commands, e-mail: gitbox-h...@hive.apache.org