Common ground for RedisClient, RedisClusterClient, RedisSentinelClient

[oscar-besga-panel]

Hi

I'm looking at the new classes RedisClient, RedisClusterClient, RedisSentinelClient in the 7.2.0 release. They operate like the old JedisPooled, more or less.
But because I'm working on a utilities library, JedisExtraUtils, using one of the will limit how the users can interact with my code.

So, to use a common class, I should go with UnifiedJedis; which covers all the Redis commands and is the parent of all three.
Then the client can use one or another freely.

Is my approach rigth ?

https://github.com/oscar-besga-panel/JedisExtraUtils

[uglide]

Hi @oscar-besga-panel
Yes, you're right. You should use UnifiedJedis if you want to support all new client classes in your code. Important note here is that you do not use UnifiedJedis constructors directly, because we plan to remove all public constructors for UnifiedJedis in future releases.

[oscar-besga-panel]

Ok
No, I will use only UnifiedRedis at the constructors of my classes, so they can be created with RedisClient, RedisClusterClient, etc.
In the integration tests I will use a RedisClient.Builder, but that's only for this case

Thanks and happy year