You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/02/20 15:06:03 UTC

[jira] [Updated] (AMBARI-22947) All Container-executor.cfg properties should be managed by ambari ui

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

ASF GitHub Bot updated AMBARI-22947:
------------------------------------
    Labels: pull-request-available  (was: )

> All Container-executor.cfg properties should be managed by ambari ui
> --------------------------------------------------------------------
>
>                 Key: AMBARI-22947
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22947
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Yesha Vora
>            Assignee: Sandor Molnar
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, only few properties from Container-executor.cfg can be managed via ambari UI. 
> Container-executor.cfg should be handled similar to yarn-env.sh in ambari.
> This way ambari ui can manage all config properties for Container-executor.cfg



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)