-
Notifications
You must be signed in to change notification settings - Fork 47
IndexError: list index out of range while applying filter on semantic cache check #203
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
Comments
For some reason, the result coming back from the cache check step is empty. We need steps to be able to reproduce the entire flow. Can you clear the db and then re-initialize your |
hey @tylerhutcherson, I emptied the Redis database and tried running the code again. The data is successfully stored in Redis, but there's an issue during retrieval. |
We're taking a closer look, thanks! |
Hi. Can you share with us your redis version, redisvl version, client versions, python version? |
redis==5.0.8 |
We're having trouble reproducing your error. Can you confirm your 'redis_url' matches what is shown if you print |
also please validate which distribution of redis you are using? |
@justin-cechmanek here is the output of <redis.client.Redis(<redis.connection.ConnectionPool(<redis.connection.Connection(host=redis-14645.c275.us-east-1-4.ec2.redns.redis-cloud.com,port=14645,db=0)>)>)> |
@tylerhutcherson I'm new to Redis and still getting familiar with its features. I've recently read the documentation here, signed up for Redis Cloud, created a database and Redis URL, and installed RedisInsight to monitor and manage my setup. Everything is working well for semantic search, but I'm encountering an issue when applying specific filters. I’m running this on an Ubuntu . |
Are you only seeing errors when working with specific filters, or do all cache checks fail to return results? |
@justin-cechmanek When I use the filters, I get an error, but without the filter, it works perfectly fine. You can see in the picture that I commented out the filter_expression, and it starts working. |
@MeharRamzan My theory is that there is an index with the name
^^ That means the index is already configured in Redis (potentially, at some point without the filter field). And thus, it's not overwriting it since it's trying to use the same name To confirm, try either:
If confirmed, we will work to make this handled better in a patch release along with better documentation. |
@tylerhutcherson I tried it again with a new database. I deleted the old one and then tried, and now it is working. |
I am facing this issue while trying to applying filter on semantic cache check


The text was updated successfully, but these errors were encountered: