You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2017/08/14 18:49:00 UTC

[jira] [Commented] (HIVE-17315) Make the DataSource used by the DataNucleus in the HMS configurable using Hive properties

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

Thejas M Nair commented on HIVE-17315:
--------------------------------------

[~zsombor.klara]
+1 I think this would be useful for TxnHandler.java also which doesn't use Datanucleus. (cc [~ekoifman] [~anishek])

bq. However since these configurations may contain sensitive information (passwords) these properties should not be displayable or manually settable.
javax.jdo.option.ConnectionPassword is currently used to supply the password for metastore. Why do we need to use connection pool specific properties to pass in the password ? 

bq. these can only be configured using proprietary xml files and not through hive-site.xml like DataNucleus.
Just to clarify the properties that can be controlled via "datanucleus.connectionPool.*" settings are configurable through hive-site.xml. But I assume there are some additional connection pool properties which are not supported through that means, which you are trying to support. Is that right ?


> Make the DataSource used by the DataNucleus in the HMS configurable using Hive properties
> -----------------------------------------------------------------------------------------
>
>                 Key: HIVE-17315
>                 URL: https://issues.apache.org/jira/browse/HIVE-17315
>             Project: Hive
>          Issue Type: New Feature
>    Affects Versions: 3.0.0
>            Reporter: Barna Zsombor Klara
>            Assignee: Barna Zsombor Klara
>
> Currently we may use several connection pool implementations in the backend (hikari, dbCp, boneCp) but these can only be configured using proprietary xml files and not through hive-site.xml like DataNucleus.
> We should make them configurable just like DataNucleus, by allowing Hive properties prefix by hikari, dbcp, bonecp to be set in the hive-site.xml. However since these configurations may contain sensitive information (passwords) these properties should not be displayable or manually settable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)