We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
when upgrading from 0.4 to 0.9, creating an existing index raised a ResponseError. is there a way to check if index exist without an exception?
The text was updated successfully, but these errors were encountered:
First of all, if you are upgrading between 0.4 and 0.9 you need to delete the data and start fresh.
Second, the way to check the existence of an index is to call FT.INFO on it, and if the index does not exist you receive an error.
FT.INFO
So basically:
try: client.info() except ResponseError: client.create_index(...)
Sorry, something went wrong.
I'm closing the issue as this doesn't seem to be a bug.
I might change the key naming in a future version in a way that the usual redis EXISTS and TYPE commands will apply to inverted indexes.
No branches or pull requests
when upgrading from 0.4 to 0.9, creating an existing index raised a ResponseError.
is there a way to check if index exist without an exception?
The text was updated successfully, but these errors were encountered: