5.0.3
Release Date: January 22, 2021
- A bug affecting this version of the Java client has been identified. If your application uses scans, but does not use
Policy.priority,ScanPolicy.scanPercentorScanPolicy.failOnClusterChange, you can safely upgrade to Java client 5.1.11. We strongly recommend that you do so at the earliest opportunity.
New Features
- Support optional connectTimeout policy. If connectTimeout greater than zero, it will be applied to creating a connection plus optional user authentication. [CLIENT-1407]
- Allow async command argument eventLoop to be null. If null, round-robin event loop distribution (eventLoops.next()) is used to set eventLoop. [CLIENT-1430]
- Start HashWheeledTimer as soon as async event loop starts running.
Bug Fixes
- Reset peers, partition and rebalance generations on node tend errors. This forces a client node refresh when a node is quickly restarted with the same generation, but with different peers, partition maps or rack nodes. [CLIENT-1391]
- Check for null value in Record.getGeoJSONString().
- Deprecate Record.getGeoJSON(). Use Record.getGeoJSONString() instead.
- Use non-atomic increment in async examples/tests when counter is only modified by a single event loop thread.
Full Changelog: 5.0.2...5.0.3