Pipelining with connection pooling

[ExploreNcrack]

Hi @mp911de
From the doc:
"The AutoFlushCommands state cannot be set on pooled connections by the Lettuce connection pooling."
I am a bit confused here does this mean that we cannot set AutoFlushCommands even after we obtain a connection from the connection pool?
for example:
is this not allowed?

RedisClient client = RedisClient.create(RedisURI.create(host, port));

GenericObjectPool<StatefulRedisConnection<String, String>> pool = ConnectionPoolSupport
               .createGenericObjectPool(() -> client.connect(), new GenericObjectPoolConfig());

// executing work
try (StatefulRedisConnection<String, String> connection = pool.borrowObject()) {
    try { 
      RedisAsyncCommands<String, String> commands = connection.async();
  
      // disable auto-flushing
      commands.setAutoFlushCommands(false);
      // perform a series of independent calls
      List<RedisFuture<?>> futures = Lists.newArrayList();
      for (int i = 0; i < iterations; i++) {
          futures.add(commands.set("key-" + i, "value-" + i));
          futures.add(commands.expire("key-" + i, 3600));
      }
      
      // write all commands to the transport layer
      commands.flushCommands();
    } catch() {
    
    } finally {
        commands.setAutoFlushCommands(true);
    }
}

What would be the correct way of leveraging pipelining with connection pooling?

[mp911de]

Lettuce applies pipelining out of the box. Auto-flush is to group commands to bigger packets and have manual control over when the command is sent to redis.