You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Oleg Nechiporenko (JIRA)" <ji...@apache.org> on 2013/10/31 21:07:18 UTC
[jira] [Updated] (AMBARI-3644) App.ServiceConfig needs
'defaultsProvider' mechanism
[ https://issues.apache.org/jira/browse/AMBARI-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Nechiporenko updated AMBARI-3644:
--------------------------------------
Attachment: AMBARI-3644.patch
> App.ServiceConfig needs 'defaultsProvider' mechanism
> ----------------------------------------------------
>
> Key: AMBARI-3644
> URL: https://issues.apache.org/jira/browse/AMBARI-3644
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.2
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Fix For: 1.4.2
>
> Attachments: AMBARI-3644.patch
>
>
> {{App.ServiceConfig}} needs to have a 'defaultsProvider' property, which will give an object extending {{App.DefaultsProvider}} class. {{App.DefaultsProvider}} class will have a method 'getDefaults(App.ServiceConfigProperty[])'. This 'defaultsProvider' will be set via {{data/service_configs.js}} only for YARN service.
> {{App.YARNDefaultsProvider}} will look at cluster setup, the provided properties, and provide an object where keys are property-names, and values are the recommended defaults.
> These defaults will then be used during cluster install as default values.
--
This message was sent by Atlassian JIRA
(v6.1#6144)