GeoCoordinates - contribute longitude and latitude command arguments Value, KeyValue, and ScoredValue that are encoded to their value, key and value and score and value representation using RedisCodec. Providing CompositeParameter will ontribute multiple command arguments by invoking the CompositeParameter.build(CommandArgs) method. Types implementing io. - Lettuce comes with a set of command argument types such as BitFieldArgs, SetArgs, SortArgs, … that can be used as parameter. Map - key and value encoding of key-value pairs using RedisCodec. ProtocolKeyword is useful to declare/reuse commonly used Redis keywords, see io. and io. ProtocolKeyword - using its byte-representation. RedisURI.toString() renders masked password.ĬmandLatenc圜ollector(…) refactored into mandLatencyRecorder(…) returning CommandLatencyRecorder. Use Spring Data Redis for a seamless Spring integration with Lettuce.ĪsyncConnectionPoolSupport.createBoundedObjectPool(…) methods are now blocking to await pool initialization.ĭecodeBufferPolicy for fine-grained memory reclaim control.
Xpending methods return now List and PendingMessages Removal of deprecated API including timeout methods accepting TimeUnit.
Refined Scripting API accepting the Lua script either as byte or String.Ĭonnection and Queue failures now no longer throw an exception but properly associate the failure with the Future handle. Support for RESP3 usage with Redis 6 along with RESP2/RESP3 handshake and protocol version discovery.ĪCL authentication using username and password or password-only authentication.Ĭluster topology refresh is now non-blocking. Performance Degradation using the Reactive API with a single connection Excessive Memory Usage or RedisException while disconnected blpop(Duration.ZERO, …) gives RedisCommandTimeoutException Switching between at-least-once and at-most-once operations Certificate Chains/Root Certificate/Self-Signed Certificates Working with dynamic Redis Command Interfaces Master/Replica connections ("Master/Slave") Connection Count for a Redis Cluster Connection Object Execution of commands on one or multiple cluster nodes Cross-slot command execution and cluster-wide execution for selected commands Static Master/Replica with predefined node addresses Coroutines API based on reactive operations How does Reactive translate to Coroutines?
0 kommentar(er)
