Support transactions

[Yury-Fridlyand]

Depends on:

• Java - Add custom command interface; and BaseCommands #58
• Add support for RESP3 types (Part 1) #55
• basic commands (get/set) - no PR yet

    var regularClient =
        RedisClient.CreateClient(
                RedisClientConfiguration.builder()
                    .address(NodeAddress.builder().build())
                    .requestTimeout(3000)
                    .build())

    var res =
        regularClient
            .customTransaction(new String[][] {{"set", "kkk", "vvv"}, {"get", "kkk"}})
            .get();

returns Object[2] with 2 strings: OK and vvv.

[acarbonetto]

I'd prefer not to expect users to create a 2D array of Strings

[acarbonetto]

what about exposing?

CompletableFuture<Object[]> customTransaction(Transaction transaction);

This is what the node client does: https://github.com/Bit-Quill/glide-for-redis/blob/46f831c5d2b31a667f7d7c53035b99e8b3851f26/node/src/RedisClient.ts#L98

[acarbonetto]

We may have to create a Transactions class that implements BaseCommands that adds the transaction calls to the list.
Maybe also a ClusterTransactions class that implements BaseClusterCommands too...

reference: https://github.com/Bit-Quill/glide-for-redis/blob/main/node/src/Transaction.ts#L72

[acarbonetto]

why not run it in the same thread?

[acarbonetto]

how does this work routes? Each command gets a route, right?
I think the API.Command object can be used to pass that in, and there will be a third argument in prepareRedisCommand that takes a command.getRouteOption(), right?

[Yury-Fridlyand]

According to protobuf - route set to the entire request

[acarbonetto]

Ah. That makes sense.