zhangmeng916 opened a new pull request #729: Implement Helix API for updating customized state URL: https://github.com/apache/helix/pull/729 ### Issues - [X] My PR addresses the following Helix issues and references them in the PR description: (#728 ) ### Description - [X] Here are some details about my PR, including screenshots of any UI changes: Currently, Helix only supports a single state for every partition. There're increasing requests from customers to have more than one state, which is defined in Helix state model, for their practical use. For example, they may want to have read/write state, quota state, version state, etc. Helix will introduce the concept of customized state, which allows customer to define the states they are interested. This PR is to implement Helix API for customers to import their customized state. The customized state is adjacent to CURRENT_STATE as a separate znode. Under this znode, there are children znodes representing each individual customized state. And each customized state is categorized by resources. ### Tests - [X] The following tests are written for this issue: TestCustomizedStateUpdate.java - [X] The following is the result of the "mvn test" command on the appropriate module: (Copy & paste the result of "mvn test") ### Commits - [X] My commits all reference appropriate Apache Helix GitHub issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 1. Subject is limited to 50 characters (not including Jira issue reference) 1. Subject does not end with a period 1. Subject uses the imperative mood ("add", not "adding") 1. Body wraps at 72 characters 1. Body explains "what" and "why", not "how" ### Code Quality - [X] My diff has been formatted using helix-style.xml
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
