GH-9720 - The new load balancer code was doing a direct string match for determining two same hosts. This is not right specially for localhost and loopback addresses. Therefore this change is doing InetAddress equals now.
GH-9718 - The load balancer code while processing the new load balance properties like 'topology-keys' and 'load-balance' properties was not handling malformed url with empty values therefore the exception. Now the new behaviour is to log a warning and then fallback to original behaviour which connects to the database without using the new load balance behaviour.
All Submissions:
[✅] Have you followed the guidelines in our Contributing document?
[✅] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
New Feature Submissions:
[✅] Does your submission pass tests?
[✅] Does mvn checkstyle:check pass ?
[ ] Have you added your new test classes to an existing test suite?
Changes to Existing Features:
[✅] Does this break existing behaviour? If so please explain.
[✅] Have you added an explanation of what your changes do and why you'd like us to include them?
[✅] Have you written new tests for your core changes, as applicable?
[✅] Have you successfully run tests with your changes locally?
GH-9720 - The new load balancer code was doing a direct string match for determining two same hosts. This is not right specially for localhost and loopback addresses. Therefore this change is doing InetAddress equals now.
GH-9718 - The load balancer code while processing the new load balance properties like 'topology-keys' and 'load-balance' properties was not handling malformed url with empty values therefore the exception. Now the new behaviour is to log a warning and then fallback to original behaviour which connects to the database without using the new load balance behaviour.
All Submissions:
New Feature Submissions:
Changes to Existing Features: