Update Config.Client to redis.UniversalClient for Cluster Support (#24) #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the
Config.Client
field inhttprateredis.Config
from*redis.Client
toredis.UniversalClient
to enable support for Redis cluster mode via*redis.ClusterClient
, addressing issue #24.Motivation:
*redis.Client
type limitshttprateredis
to single Redis instances, causing type mismatch errors when using*redis.ClusterClient
redis.UniversalClient
is a flexible interface supporting both*redis.Client
(single instance),*redis.ClusterClient
(cluster mode), and*redis.Ring (sharded Redis)
, making it suitable for broader use cases.Changes:
Config.Client
inconfig.go
from*redis.Clien
t toredis.UniversalClient
.Impact:
httprateredis
to work seamlessly with Redis cluster mode, addressing community demand in Allow other go-redis client implementations #24.*redis.Client
usage for single-instance Redis.redis.UniversalClient
implementations.