You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the latest release 6.5.0 which has the recently added redisJson commands (Thank you and Great Job!).
Using the StatefulRedisClusterConnection , I can access either RedisAdvancedClusterCommands which gives me access to RedisJsonCommands through the simple inheritance model.
However when using the async member RedisAdvancedClusterAsyncCommands , it would appear that the RedisJsonAsyncCommands was left out of RedisClusterAsyncCommandshere
If this is intentional , what would the proper path forward be to access redisJson async commands for a cluster?
The text was updated successfully, but these errors were encountered:
* Added missing ASYNC and REACTIVE interfaces for the cluster commands
* Handle container start failures more gracefully
* Attempt to start the containers three times before failing
* Added missing ASYNC and REACTIVE interfaces for the cluster commands
* Handle container start failures more gracefully
* Attempt to start the containers three times before failing
Bug Report
I am using the latest release 6.5.0 which has the recently added redisJson commands (Thank you and Great Job!).
Using the
StatefulRedisClusterConnection
, I can access eitherRedisAdvancedClusterCommands
which gives me access toRedisJsonCommands
through the simple inheritance model.However when using the async member
RedisAdvancedClusterAsyncCommands
, it would appear that theRedisJsonAsyncCommands
was left out ofRedisClusterAsyncCommands
hereIf this is intentional , what would the proper path forward be to access redisJson async commands for a cluster?
The text was updated successfully, but these errors were encountered: