Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help needed - regarding Redisearch client connection: What happens if io.redisearch.client.Client.close() is not called in Redisearch? #185

Open
chaitradalawai opened this issue May 10, 2022 · 2 comments

Comments

@chaitradalawai
Copy link

I am using Redisearch through jredisearch api for storing the data in Redisearch Indexes. Please help me know about the connection to Redis operations which we do using new Client() and client.close().
Does the new Client() establishes the connection to jedis pool?
After querying/loading the cache with newly created client object, do we have to call the client.close() each time ? What happens if the close method isn't called?
And after we close the connection using client.close(), client object has to be instantiated again or the reference to previously connected object should work?

Thank you.

@gkorland
Copy link
Contributor

gkorland commented May 10, 2022

Please notice JRediSearch is deprecated and you should use Jedis 4.2 which has built in support for RediSearch.

It now as simple as:

client.ftSearch()

@chaitradalawai
Copy link
Author

thanks.
But could you please explain about client connection establishment and closing to jedis pool.

Does the new Client() establishes the connection to jedis pool?
After querying/loading the cache with newly created client object, do we have to call the client.close() each time ? What happens if the close method isn't called?
And after we close the connection using client.close(), client object has to be instantiated again or the reference to previously connected object should work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants