Mark Paluch

We've been regularly trying to come up with a good model to express customization approaches. Query by Example is much more constrained than Querydsl and so a reduced functionality scope...

Care to move this documentation bit to `RedisOperations`? And please cross-check `ReactiveRedisOperations` for the same mention.

Thank you for your contribution. That's merged, polished, and backported now.

That's merged and polished now. For the time being, I suggest keeping that change for 4.0 only and if it proves to not create downstream issues, we can consider it...

Initially, we decided against module support because modules and clients weren't coupled and we do not have the bandwidth to support any kind of module. In the past year, Redis...

@tishun I've assigned the ticket to you. Let's have a chat soon about the design and iterative planning how to get going here (and what use-cases we would like to...

`discardIfNecessary` resets the Redis transaction state using Redi's `DISCARD` command. `pool.returnObject(…)` is what you're looking for. You need to configure pool object validation via `GenericObjectPoolConfig.testOnBorrow` to check for connected Redis...

One idea could be introducing a validation function or a depth of validation. For this to work, the Lettuce driver would need to introduce a `Predicate` to `ConnectionPoolSupport`.

Thanks for your pull request. This is interesting but we don't have currently the bandwidth to evolve JDBC support. We will come back to this one next year or so.

Redis doesn't have the friendliest protocol as each thing we send to the server is considered a command. There's no ping frame or similar that would yield a response even...