-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Materialization and serving fail when using Redis cluster for the online store #2297
Comments
hey @vstrimaitis thanks for reporting this issue and for the detailed investigation! we'll take a look at this ASAP |
Looks like this is still broken since we rolled back the PR due to some issues with the new version of redis clusters (see bug on redis-py: redis/redis-py#2003). Might need to roll back to redis-py-cluster to make this work properly |
Confirming that I'm also seeing this issue with Feast=0.18.1. |
See #2347 for a rollback PR |
I solved this issue,here is my code |
Expected Behavior
Using a Redis cluster as the online storage should work without errors.
Current Behavior
Using a Redis cluster as the online storage no longer works after updating from 0.17.0 to 0.18.0. The issue happens whenever Feast tries to connect to the Redis cluster - e.g. during
feast materialize
or during feature serving. The exact error that is raised looks like this:Steps to reproduce
feast materialize
Specifications
Possible Solution
Some investigation revealed that versions 0.17.0 and 0.18.0 differ in the sense that 0.18.0 uses
RedisCluster
fromredis.cluster
instead ofrediscluster
. As a result, the code here breaks because the newRedisCluster
instance expects to receive a list ofClusterNode
instead of a list of dicts. Temporarily we worked around this issue by creating a custom online store (by copying all of the code in the linked file 😁 ) and changing it like so:This worked for us, but I'm not sure if this is the best approach in general because I'm not too familiar with the codebase yet.
The text was updated successfully, but these errors were encountered: