You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2013/05/02 01:50:16 UTC
[jira] [Updated] (AMBARI-2069) Allow service components to be
deployed with separate configuration paths
[ https://issues.apache.org/jira/browse/AMBARI-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yusaku Sako updated AMBARI-2069:
--------------------------------
Summary: Allow service components to be deployed with separate configuration paths (was: Allow service components to be deployed with seprate configuration paths)
> Allow service components to be deployed with separate configuration paths
> -------------------------------------------------------------------------
>
> Key: AMBARI-2069
> URL: https://issues.apache.org/jira/browse/AMBARI-2069
> Project: Ambari
> Issue Type: Bug
> Components: agent, controller
> Affects Versions: 1.3.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.4.0
>
>
> Background:
> We changed the permissions on hive-site.xml from 644 to 660. This was done because the metastore password is in clear text.
> This results in clients not being able to access the metastore and hive cannot run in client mode. Recomended aproach is splitting the hive configs differently for client and hive metastore host.
> The password is required only for the metastore process and the hive client config should be readable to all.
> This cannot be achieved currently because the rpm deploys the components with dedicated symbolic links to config files, example,
> ]# ls -al /usr/lib/hive/
> lrwxrwxrwx 1 root root 14 May 1 23:11 conf -> /etc/hive/conf
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira