You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Juanjo Marron (JIRA)" <ji...@apache.org> on 2017/04/27 22:12:04 UTC

[jira] [Assigned] (AMBARI-20454) Some Ambari configuration should be managed similar to other configuration

     [ https://issues.apache.org/jira/browse/AMBARI-20454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juanjo Marron reassigned AMBARI-20454:
--------------------------------------

    Assignee: Juanjo Marron

> Some Ambari configuration should be managed similar to other configuration 
> ---------------------------------------------------------------------------
>
>                 Key: AMBARI-20454
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20454
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-server, ambari-web
>            Reporter: Tuong Truong
>            Assignee: Juanjo Marron
>
> Currently, Ambari has a number of configuration in ambari.properties and quite a few other such as service check time out, directory permission that are hard coded.     This make it hard to manage Ambari customization to better work with the cluster.    Many of these properties should be managed in Ambari similar to service configuration for better version control, and upgrading from release to release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)