[
https://issues.apache.org/jira/browse/HELIX-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770994#comment-13770994
]
Kanak Biscuitwala commented on HELIX-98:
----------------------------------------
Resolving this by adding addStateConstraint and addTransitionConstraint to the
ClusterConfig builder for the new API. Also added new builders for state and
message types that wrap the existing builder.
> clean up setting constraint api
> -------------------------------
>
> Key: HELIX-98
> URL: https://issues.apache.org/jira/browse/HELIX-98
> Project: Apache Helix
> Issue Type: Sub-task
> Components: helix-core, helix-webapp-admin
> Reporter: Zhen Zhang
> Assignee: Kanak Biscuitwala
> Fix For: 0.6.2-incubating
>
>
> currently setting constraint is doing through the following api:
> 1) constraint builder
> builder.addConstraintAttribute(key1, value1).addConstraintAttribute(key2,
> value2)....
> 2) add constraint to cluster
> admin.addConstraint(clusterName, constraintType, constraintId, constraint)
> will be better to have:
> 1)
> builder(id).forMsgType(msgType).forInstance(instanceName).setConstraint(contraintValue)
> 2) add constraint to cluster
> admin.addMsgConstraint(clusterName, constraint)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
