mgao0 opened a new pull request #912: Add integration test to customized view aggregation URL: https://github.com/apache/helix/pull/912 ### Issues - [ ] My PR addresses the following Helix issues and references them in the PR description: This PR added an integration test to customized view aggregation. The integration test involves components: update customized state using customized view provider, and use routing table provider to listen to changes in customized view which is aggregated in controller. ### Description - [ ] Here are some details about my PR, including screenshots of any UI changes: This integration test involves the following steps: 1. update/delete customized state to ZK 2. update/delete the same customized state in a local recorded map 3. configure the customized state types to be listened by routing table provider 4. update the same customized state types to a local recorded set which represents the customize state types that are currently being listened 4. get customized views from routing table provider 5. compare customized state values in the customized views fetched by routing table provider, and in local recorded map; also compare the customized state types available from ZK and local set ### Tests - [ ] The following is the result of the "mvn test" command on the appropriate module: [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 85.425 s - in org.apache.helix.integration.TestCustomizedViewAggregation [INFO] [INFO] Results: [INFO] [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 01:29 min [INFO] Finished at: 2020-03-25T21:05:05-07:00 [INFO] -------------------------------------------- ### Commits - [ ] My commits all reference appropriate Apache Helix GitHub issues in their subject lines. 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 - [ ] My diff has been formatted using helix-style.xml (helix-style-intellij.xml if IntelliJ IDE is used)
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@helix.apache.org For additional commands, e-mail: reviews-h...@helix.apache.org
