[ 
https://issues.apache.org/jira/browse/HIVE-16383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963849#comment-15963849
 ] 

Lefty Leverenz commented on HIVE-16383:
---------------------------------------

Doc note:  This changes the default value and list of possible values for 
*datanucleus.connectionPoolingType* and adds 
*datanucleus.connectionPool.maxPoolSize* to HiveConf.java, so the wiki will 
need to be updated for release 3.0.0.

* [Configuration Properties -- MetaStore | 
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-MetaStore]
* [Configuration Properties -- MetaStore -- datanucleus.connectionPoolingType | 
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-datanucleus.connectionPoolingType]

Added a TODOC3.0 label.

Formatting note:  The description of *datanucleus.connectionPool.maxPoolSize* 
is 6 lines long but will appear on a single line in the generated template file 
because \n wasn't used for line breaks.  Can this be fixed?

* [AdminManual Configuration -- hive-site.xml and hive-default.xml.template | 
https://cwiki.apache.org/confluence/display/Hive/AdminManual+Configuration#AdminManualConfiguration-hive-site.xmlandhive-default.xml.template]

> Switch to HikariCP as default connection pooling
> ------------------------------------------------
>
>                 Key: HIVE-16383
>                 URL: https://issues.apache.org/jira/browse/HIVE-16383
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>    Affects Versions: 3.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>              Labels: TODOC3.0
>             Fix For: 3.0.0
>
>         Attachments: HIVE-16383.1.patch, HIVE-16383.2.patch
>
>
> Since 3.0 is planned to move to JDK8, we can now switch to HikariCP as 
> default connection pooling for DN because of its improved performance over 
> others. 



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

Reply via email to