zhangmeng916 opened a new pull request #934: Add cache update/delete in 
customized view aggregation stage
URL: https://github.com/apache/helix/pull/934
 
 
   ### Issues
   
   - [X] My PR addresses the following Helix issues and references them in the 
PR description:
   
   (#888 )
   
   ### Description
   
   - [x] Here are some details about my PR, including screenshots of any UI 
changes:
   
   This PR adds the customized view cache update/delete operation in customized 
view aggregation stage. Previously, we depend on routing table provider to 
update customized view cache, and we found there're some cases we see 
inconsistency between cache and zk due to the lag between routing table 
provider and controller. To handle cache in the customized view aggregation 
stage could avoid such problems.
   
   ### Tests
   
   - [ ] 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. 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 
   (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:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to