You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@helix.apache.org by GitBox <gi...@apache.org> on 2022/03/30 21:40:00 UTC
[GitHub] [helix] xyuanlu opened a new pull request #2001: add type and reason for batch disable/enable
xyuanlu opened a new pull request #2001:
URL: https://github.com/apache/helix/pull/2001
### Issues
- [X] My PR addresses the following Helix issues and references them in the PR description:
#2000 Batch enabling/disable instance with type and reason
### Description
- [X] Here are some details about my PR, including screenshots of any UI changes:
Helix already have a batch instance enable/disable feature but it is inactive now. This change make this feature active now as the dependency is resolved. Helix should also allow user to set disabled type and reason for these instances.
Helix-rest side change will be added in follow up PR. So feature depends on this PR can be unblocked.
### Tests
- [X] The following tests are written for this issue:
Enabled :
TestBatchEnableInstances
Extended :
TestBatchEnableInstances.testBatchDisableOldEnable
- The following is the result of the "mvn test" command on the appropriate module:
(If CI test fails due to known issue, please specify the issue and test PR locally. Then copy & paste the result of "mvn test" to here.)
### Changes that Break Backward Compatibility (Optional)
- My PR contains changes that break backward compatibility or previous assumptions for certain methods or API. They include:
(Consider including all behavior changes for public methods or API. Also include these changes in merge description so that other developers are aware of these changes. This allows them to make relevant code changes in feature branches accounting for the new method/API behavior.)
### 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.
To unsubscribe, e-mail: reviews-unsubscribe@helix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@helix.apache.org
For additional commands, e-mail: reviews-help@helix.apache.org
[GitHub] [helix] xyuanlu closed pull request #2001: Add type and reason for batch disable/enable instance
Posted by GitBox <gi...@apache.org>.
xyuanlu closed pull request #2001:
URL: https://github.com/apache/helix/pull/2001
--
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.
To unsubscribe, e-mail: reviews-unsubscribe@helix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@helix.apache.org
For additional commands, e-mail: reviews-help@helix.apache.org