You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2013/11/06 03:30:17 UTC
[jira] [Updated] (AMBARI-3699) App.ServiceConfig needs
'configsValidator' validating across service values
[ https://issues.apache.org/jira/browse/AMBARI-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srimanth Gunturi updated AMBARI-3699:
-------------------------------------
Attachment: AMBARI-3699.patch
> App.ServiceConfig needs 'configsValidator' validating across service values
> ---------------------------------------------------------------------------
>
> Key: AMBARI-3699
> URL: https://issues.apache.org/jira/browse/AMBARI-3699
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.2
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 1.4.2
>
> Attachments: AMBARI-3699.patch
>
>
> We have many properties whose values are interdependent. We have no mechanism to validate multiple properties in a service. We need to have a 'configsValidator' filed set in {{App.ServiceConfig}} class via {{data/service_configs.js}}. This field will have an object extending {{App.ServiceConfigsValidator}} class. This class will have one method - {{validateConfigs(App.ServiceConfigProperty[])}} which will validate the interdependencies between properties and mark them invalid if necessary with appropriate message.
> For now only {{App.YARNServiceConfigsValidator}} will be implemented.
--
This message was sent by Atlassian JIRA
(v6.1#6144)