Redis URI timeout seems to be a maximum value and not a default value. #271

@guperrot

Description

Hi,

RedisURI has a "timeout for synchronous command execution".

But when using the async API, calling get with a timeout value greater than the redis URI timeout does not work, the redis URI timeout is used no matter what.

Does that mean the redis URI timeout Javadoc is actually misleading and is rather a maximum timeout for any command whether the used API is sync or async?

Another issue I have is integrating lettuce with brpop: brpop has a timeout of its own at Redis protocol level, but actually when passing 0 for "wait forever", the java API throws a timeout exception after the redis uri configured timeout (which defaults to 1 minute). How can I avoid that redis URI timeout to take over?