You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2017/10/02 20:27:00 UTC
[jira] [Comment Edited] (HIVE-13842) Expose ability to set number
of connections in the pool in TxnHandler
[ https://issues.apache.org/jira/browse/HIVE-13842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188672#comment-16188672 ]
Eugene Koifman edited comment on HIVE-13842 at 10/2/17 8:26 PM:
----------------------------------------------------------------
This is now possible via _datanucleus.connectionPool.maxPoolSize_ since HIVE-16383
was (Author: ekoifman):
This is now possible via _datanucleus.connectionPool.maxPoolSize_ since hive-16383
> 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
> Assignee: 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.4.14#64029)