access to RedisClusterClient/RedisClient

[jmhodges]

I was trying to use this wonderful library but the app I'm working on needs access to the underlying RedisClusterClient in order to handle connection pooling. I can see that there's lots of useful things done with the StatefulRedisClusterConnection before it's returned, so I understand that this is possibly outside the scope of the project.

But it would be nice to get all this great JSON config work while will getting the Client I needed.

[natalie-zamani]

Hi @jmhodges! Thanks for the kind words! 😃

When in the lifecycle of the client setup would you need access to the RedisClusterClient? If we added a way to override the existing factory and plug your functionality in, would that meet your needs?

[jmhodges]

Oh, lemme narrow the focus to RedisClient and let's ignore the "connection pooling" stuff, because I was still learning a legacy codebase this is going in:

We want to get access to pubsub stuff with redisClient.connectPubSub and MasterClient.connect(redisClient, ...)

[natalie-zamani]

@jmhodges That seems totally reasonable! One way this can be easily addressed is by adding a protected method that will allow you to extend RedisClusterClientFactory/RedisClientFactory and add whatever logic you need to perform on the RedisClient.

One follow-up question: do you simply need to configure additional things on the RedisClient, or do you actually need to be given the client itself to use in your application logic?

[JKomoroski]

Not sure if directly related, but I too was hoping to use this for Pub/Sub.