add support for xautoclaim

[7ravis]

hi. I'm using Spring Boot 2.6.6. right now, in order to run the xautoclaim command, I have to get the native lettuce client and use a lettuce command interface . I would prefer to use Spring's higher-level Reactive/StreamOperations interface, but xautoclaim is not currently supported. please add Reactive/StreamOperations support for xautoclaim. on my Spring version, regular xclaim is also not supported in Reactive/StreamOperations, but it's supported in Reactive/StreamCommands. if, for some reason, there is less resistance to add xautoclaim at the Reactive/StreamCommands level, that would also be preferable to what I'm currently doing. thanks!

[hemju]

Would be nice to have xautoclaim supported. Any news for which version it is planned?

[softprog]

how this issue,please

[RomainWilbert]

At this point, using xautoclaim causes a direct dependency to the redis client :(

[kkocel]

I've ended up with getting a client from LettuceConnectionFactory and calling it directly:

    private val xAutoClaimArgs: XAutoClaimArgs<String> =
        XAutoClaimArgs.Builder
            .xautoclaim(
                Consumer.from(consumerGroupName, consumerName),
                messageDuration,
                "0-0",
            ).count(messagesToClaim)

    private val commands = commands(lettuceConnectionFactory.requiredNativeClient)

    private fun commands(client: AbstractRedisClient): RedisClusterCommands<String, String> =
        when (client) {
            is RedisClient -> {
                client.connect().sync()
            }
            is RedisClusterClient -> {
                client.connect().sync()
            }
            else -> {
                throw IllegalArgumentException("Unsupported Redis client type")
            }
        }

    fun reclaim(): MutableList<StreamMessage<String, String>> =
        commands.xautoclaim(streamName, xAutoClaimArgs).messages
        }

[ivan-kripakov-m10]

Hello,
It seems the issue is still relevant, as there is currently no support for the xautoclaim command. I am interested in contributing to this, but I have a few questions to clarify before:

1. Are there any existing plans that might block or conflict with this functionality addition?
2. If not, would you prefer the xautoclaim command to support cursor-like behavior, or would simply returning the RecordId to be used as a start argument in the next call be sufficient?

[kkocel]

@ivan-kripakov-m10 Hi, I started adding this feature as well - it's WiP - feel free to base your work on it or fork my main: e94fdd4

There are some issues related to xautoclaim - for instance, Lettuce does not fully support this command - it does not provide deleted entries.

As for your second question - I added new class that stores record id and lists of claimed and deleted entries

[ivan-kripakov-m10]

@kkocel Hi,
Did you discuss the solution plan with the team?
The answer to the second question can significantly impact both solution and library client code.