M Sazzadul Hoque

@gkorland redis-om-spring is using JRediSearch at this moment. Perhaps we can wait for some time before removing it.

Bump - https://github.com/RediSearch/RediSearch/issues/2700, https://github.com/redis/jedis/issues/2974

@shannonantony Please check (and focus) on `Failed to create socket`. There seems to be some issues when creating the connections. And given information is not enough even to guess.

From now on, [`ClientUtil`](https://github.com/RediSearch/JRediSearch/blob/master/src/main/java/io/redisearch/client/util/ClientUtil.java).toStringMap(...) should come in handy.

@pinkfloydsito At this moment, this is the way to do. And this is happening in [RediSearch](https://github.com/RediSearch/RediSearch). JRediSearch alone can't resolve this.

> Have you somebody tried override `RedisModulesClient` for cluster support? @viktorzavadil No.

I agree with @bsbodden. Ping @chayim for the final say?

@robben009 Your jedis connections are being managed by [spring-data-redis](https://github.com/spring-projects/spring-data-redis). That may be a better place to ask.

@cjdxhjj You are trying to use RedisJSON v2 patterns. JRedisJSON only supports RedisJSON v1. You may consider using [Jedis](https://github.com/redis/jedis). To use RedisJSON v2 patterns there, you would have to use...

@gkorland Wasn't this PR just to test the latency issue? Are you considering merging it?