qqu0127 opened a new pull request, #2478: URL: https://github.com/apache/helix/pull/2478
### Issues - [X] My PR addresses the following Helix issues and references them in the PR description: Fixes https://github.com/apache/helix/issues/2299 ### Description - [X] Here are some details about my PR, including screenshots of any UI changes: Without the fix, the class `AssignableReplica` is breaking the contract in `Object.hashCode()`. If only override `equals()`, a hashset may contain two equaled objects. See also https://stackoverflow.com/questions/2265503/why-do-i-need-to-override-the-equals-and-hashcode-methods-in-java. Overriding hashCode() in `AssignableReplica` to make it consistent with `equals()`. Also changing the appearance of `Set<AssignableReplica>` to `List`, which is the way it should be. In most use cases there is a collection of replicas with same (resource, partition, state), using hashset is confusing to start with. This class is fundamental to WAGED rebalancer. Using list also has performance improvement over set. ### 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: [INFO] Tests run: 1326, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6,965.344 s - in TestSuite [INFO] [INFO] Results: [INFO] [INFO] Tests run: 1326, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] [INFO] --- jacoco-maven-plugin:0.8.6:report (generate-code-coverage-report) @ helix-core --- [INFO] Loading execution data file /Users/qqu/workspace/qqu-helix/helix-core/target/jacoco.exec [INFO] Analyzed bundle 'Apache Helix :: Core' with 797 classes [INFO] [INFO] --- maven-bundle-plugin:5.1.4:bundle (default-bundle) @ helix-core --- ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
