zhouyifan279 opened a new issue #1091:
URL: https://github.com/apache/incubator-kyuubi/issues/1091


   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   
   
   ### Search before asking
   
   - [X] I have searched in the 
[issues](https://github.com/apache/incubator-kyuubi/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### Describe the feature
   
   Enhance `HiveDelegationTokenProvider` to renew delegation tokens of multiple 
Hive metastore clusters.
   
   ### Motivation
   
   Kyuubi supports [setting Hive metastore uris in JDBC connection 
URL](https://kyuubi.readthedocs.io/en/latest/deployment/hive_metastore.html#via-jdbc-connection-url).
   But current `HiveDelegationTokenProvider` implemented in #1009 can only 
renew delegation tokens of Hive metastore defined in hive-site.xml.
   
   For users who frequently access different Hive metastore clusters, the 
Kyuubi engines visiting non default Hive metastore server are still limited by 
Hive token's expiration time.
   
   
   ### Describe the solution
   
   Introduce a Kyuubi configuration `kyuuib.credentials.hive.metastore.uris` to 
specify extra Hive metastore URIs.  
   URIs should be specified in format 
"thrift://host01:port01,thrift://host02:port02;thrift://host11:port11,thrift://host12:port12",
 where "," separates URIs belonging to same metastore cluster, ";" separates 
URIs of different metastore clusters.
   
    `HiveDelegationTokenProvider`  will create a `HiveMetaStoreClient` for each 
Hive metastore URIs and periodically renew the delegation tokens.
   
   ### Additional context
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to