Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 15 Aug 2017 06:22:03 +0000 (UTC)
From: "Thejas M Nair (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13094498.1502722945000.31635.1502778123230@Atlassian.JIRA>
In-Reply-To: <JIRA.13094498.1502722945000@Atlassian.JIRA>
References: <JIRA.13094498.1502722945000@Atlassian.JIRA> <JIRA.13094498.1502722945937@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HIVE-17315) Make the DataSource used by the
 DataNucleus in the HMS configurable using Hive properties
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 15 Aug 2017 06:22:14 -0000


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

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

bq. Even if the current properties are safe, I would be afraid of what could be added by future versions of the connection pool implementations, since we would be exposing these settings the moment we upgrade the library.
Other than password, I don't expect any other confidential property to be used by connection pool.
Hiding properties by default would cause difficulty in debugging issues. This is also counter to the practice we follow with other types of configs such as hdfs, yarn, tez, spark etc (ie, we don't hide those properties by default)


> 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)