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

Eugene Koifman updated HIVE-13842:
----------------------------------
    Description: 
Current defaults are hardcoded 8/10 for dbcp/bonecp

Various Connection pool managers support reading configs from a config file.

The implementation would ideally allow end user to point Hive at the manager 
specific config file to let the user have full control


HikariCP supports 
HikariConfig config = new HikariConfig("/some/path/hikari.properties");
see https://github.com/brettwooldridge/HikariCP

BoneCP supports
bonecp-config.xml
see 
https://github.com/wwadge/bonecp/blob/master/bonecp/src/main/java/com/jolbox/bonecp/BoneCPConfig.java



  was:
Current defaults are hardcoded 8/10 for dbcp/bonecp

Various Connection pool managers support reading configs from a config file.

The implementation would ideally allow end user to point Hive at the manager 
specific config file to let the user have full control


> Expose ability to set number of connections in the pool in TxnHandler
> ---------------------------------------------------------------------
>
>                 Key: HIVE-13842
>                 URL: https://issues.apache.org/jira/browse/HIVE-13842
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>            Priority: Critical
>
> Current defaults are hardcoded 8/10 for dbcp/bonecp
> Various Connection pool managers support reading configs from a config file.
> The implementation would ideally allow end user to point Hive at the manager 
> specific config file to let the user have full control
> HikariCP supports 
> HikariConfig config = new HikariConfig("/some/path/hikari.properties");
> see https://github.com/brettwooldridge/HikariCP
> BoneCP supports
> bonecp-config.xml
> see 
> https://github.com/wwadge/bonecp/blob/master/bonecp/src/main/java/com/jolbox/bonecp/BoneCPConfig.java



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to