[ 
https://issues.apache.org/jira/browse/HIVE-26702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Nauroth updated HIVE-26702:
---------------------------------
    Description: HIVE-17315 added support for more flexible metastore 
connection pooling configuration, integration with DBCP and an important 
capability to the HikariCP integration: passthrough configuration of any 
additional HikariCP configurations, such as {{{}minimumIdle{}}}. This issue 
proposes to backport all 5 sub-tasks of HIVE-17315 for inclusion in the 
upcoming 3.2.0 release.  (was: HIVE-17317 added support for using DBCP as the 
metastore's database connection pooling implementation. It also added an 
important capability to the HikariCP integration: passthrough configuration of 
any additional HikariCP configurations, such as {{{}minimumIdle{}}}. This issue 
proposes to backport this for the upcoming 3.2.0 release.)
        Summary: Backport HIVE-17315 (more flexible metastore database 
connection pooling) to 3.2.0.  (was: Backport HIVE-17317 (metastore DBCP and 
HikariCP configuration support) to 3.x.)

> Backport HIVE-17315 (more flexible metastore database connection pooling) to 
> 3.2.0.
> -----------------------------------------------------------------------------------
>
>                 Key: HIVE-26702
>                 URL: https://issues.apache.org/jira/browse/HIVE-26702
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Major
>
> HIVE-17315 added support for more flexible metastore connection pooling 
> configuration, integration with DBCP and an important capability to the 
> HikariCP integration: passthrough configuration of any additional HikariCP 
> configurations, such as {{{}minimumIdle{}}}. This issue proposes to backport 
> all 5 sub-tasks of HIVE-17315 for inclusion in the upcoming 3.2.0 release.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to