Update since tags. Move FlushOption converters to client-specific converters. Use method-references where possible.
See #2187
Original pull request: #2190.
Add support for MINID trimming. Add tests. Extract Jedis XAddParams conversion to StreamConverters.
Reorder methods. Simplify StreamRecord creation.
See #2247
Add since tags. Consistently document scan command with try-with-resources guidance. Use try-with-resources in tests.
See #2260
Original pull request: #2263.
Allow Jedis to exist pub/sub loop gracefully. Await unsubscribe. Reduce retry backoff to allow from broken connection recovery. Do not use pooling to avoid using broken connections.
See #2256
RedisMessageListenerContainer is now reimplemented using non-blocking synchronization guards and a state management to simplify its maintenances. Additionally, listener registration and subscription setup through the start() method awaits until the listener subscription is confirmed by the Redis server. The synchronization removes potential race conditions that could happen by concurrent access to blocking Redis connectors in which the registration state was guessed and not awaited.
Resolves: #964
Original Pull Request: #2256
We now retain the target type when obtaining a HashMapper through StreamObjectMapper. To achieve this, we introduced the HashObjectReader interface accepting a target type.
Resolves: #2198
Related: #1566
Original Pull Request: #2253
We now properly extract the byte array from a ByteBuffer by copying its content respecting the read position and limits.
Closes#2204
Original Pull Request: #2213
We now return a list containing a single empty KeyValue element when ReactiveHashOperations.hMGet(…) called for a single key returns no value.
Previously, the code used onErrorReturn(…) which returned the wrong value and suppressed errors.
Closes#2210
We now no longer try to cast the Lettuce connection to StatefulRedisConnection when eagerly initializing the shared connection. Instead, we now introduced another method to obtain the cluster connection.
Closes#2186
The documentation indicates that it's not possible to use the keyspace notification message listener on AWS ElastiCache. The added text describes a way to prevent Spring Data Redis from using the `CONFIG` command and make it possible to use the listener on AWS.
Closes#2181
