pkuwm opened a new pull request #1344:
URL: https://github.com/apache/helix/pull/1344


   ### Issues
   
   - [ ] My PR addresses the following Helix issues and references them in the 
PR description:
   
   Fixes #1343 
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI 
changes:
   
   In CallbackHanlder's subscribeForChanges(), children names need to be 
fetched. subscribeChildChange(path, callbackType) does actually have the 
children list, but it doesn't return, and later getChildren() is called again. 
It wastes one zk call: not only wasting time in handling a callback, but also 
adds more read pressure to zk server.
   
   We could use the return result from subscribeChildChange() and save one 
getChildren() call.
   
   This PR also adds event types logging and removes two logs. When debugging, 
we can actually use the event types to determine the code logic. No need to 
print those two logs, which saves logging overhead when there are intensive 
callbacks.
   
   ### Tests
   
   - [ ] The following tests are written for this issue:
   
   (List the names of added unit/integration tests)
   
   - [ ] The following is the result of the "mvn test" command on the 
appropriate module:
   
   (Before CI test pass, please copy & paste the result of "mvn test")
   
   ### Documentation (Optional)
   
   - In case of new functionality, my PR adds documentation in the following 
wiki page:
   
   (Link the GitHub wiki you added)
   
   ### 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:
[email protected]



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

Reply via email to