Testing conductivity in JRedisSearch to Redis without a previous created Index

The Client Class, which wraps all connection and command calls to the RediSearch module, requires an index when creating an instance.

Any Client method invocation that cannot be connected to Redis with the connection information provided when calling the constructor you will get the following exception JedisConnectionException from Jedis this exposes the jedis api to all users of the JRediseach api.

If the connection information works and there is a successfull connection but the index used is not present then any valid call to the methods in the Client class will result in various exceptions depending on the call accept the one to createIndex which will create the index.



  • dropIndex(boolean) will return false but really the api is suppressing the thrown exception that the index was not found.
  • getInfo() which will throw an “JedisDataException: Unknown Index name”.


None of these approaches are ideal but for now my vote would be to call getInfo since no harm can happen, dropIndex and others can actually alter the index if it did all ready exsist.

Reference to the API docs


PrintView Printer Friendly Version

EmailEmail Article to Friend

References (1)

References allow you to track sources for this article, as well as articles that were written in response to this article.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
Main | Microstack Developer »