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

["Eugene Koifman (JIRA)" <ji...@apache.org>]

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

Eugene Koifman edited comment on HIVE-17315 at 8/14/17 7:11 PM:
----------------------------------------------------------------

What is the intent here?  is it to support something like "bonecp.<some string that bonecp recognizes>" in hives-site.xml so that Hive sets "some string that bonecp recognizes" on the data source? (so hive doesn't interpret "some string that bonecp recognizes" in any way)



was (Author: ekoifman):
What is the intent here?  is it to support something like "bonecp.<some string that bonecp recognizes>" in hives-site.xml so that Hive sets "some string that bonecp recognizes" on the data source?


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