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
When using redis cluster,
it seems that the hash slot to which the XREADGROUP command is routed to is calculated using the consumer group rather than the stream.
This can be seen here xreadgroup in RedisCommandBuilder. where consumer.group is added to args with addKey.
Expected behavior/code
The XREADGROUP command should be routed based on stream and not consumer group.
Environment
Lettuce version(s): 6.1.8.RELEASE
Redis version: 6.x
Possible Solution
perhaps converting the consumer group and consumer name to strings and adding to xreadargs with add() instead of addKey()
The text was updated successfully, but these errors were encountered:
…mand #2140
Lettuce now encodes the consumer group and name eagerly to pass on these values as byte array instead of deferred key argument encoding to avoid the first-key detection to use consumer group or name as key argument. With this strategy, the stream name is being detected as first key.
…mand #2140
Lettuce now encodes the consumer group and name eagerly to pass on these values as byte array instead of deferred key argument encoding to avoid the first-key detection to use consumer group or name as key argument. With this strategy, the stream name is being detected as first key.
Bug Report
Current Behavior
When using redis cluster,
it seems that the hash slot to which the XREADGROUP command is routed to is calculated using the consumer group rather than the stream.
This can be seen here xreadgroup in RedisCommandBuilder. where consumer.group is added to args with addKey.
Expected behavior/code
The XREADGROUP command should be routed based on stream and not consumer group.
Environment
Possible Solution
perhaps converting the consumer group and consumer name to strings and adding to xreadargs with add() instead of addKey()
The text was updated successfully, but these errors were encountered: