[
https://issues.apache.org/jira/browse/AMBARI-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815439#comment-13815439
]
Jaimin D Jetly commented on AMBARI-3699:
----------------------------------------
+1 for the 1.4 branch 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.0, 1.4.2
>
> Attachments: AMBARI-3699.patch, AMBARI-3699_branch-1.4.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)
