You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2016/06/16 14:22:05 UTC

[jira] [Commented] (AMBARI-17223) Ability to add "javax.jdo.option.ConnectionPassword" to hive clients from ambari

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

Vitaly Brodetskyi commented on AMBARI-17223:
--------------------------------------------

Reverted patches from trunk and breanch-2.4

> Ability to add "javax.jdo.option.ConnectionPassword" to hive clients from ambari
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-17223
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17223
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17223.patch
>
>
> Problem is that they need to access the "javax.jdo.option.ConnectionPassword" password but Ambari is pushing only to /etc/hive/conf.server/hive-site.xml. I have instructed and recommended various workarounds and even suggest modifying their app. Even having a static hive-site.xm with the information they did not accept and asked to open an enhancement request. The enhancement is to allow adding "javax.jdo.option.ConnectionPassword" to hive clients from ambari and have a separate hive-site.xml path for clients.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)