| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| score = feature_value | ||
| member = redis_key_bin_with_sort_keys | ||
| zset_key = f"{project}:{table.name}:{feature_name}:{redis_key_bin}" | ||
| pipe.zadd(zset_key, {member: score}) |
There was a problem hiding this comment.
I think we should do some validation here to check if the score is numeric type or not rather than wait for Redis to throw the error. What do you think?
Sorry, something went wrong.
There was a problem hiding this comment.
Yes agree, it was in my to-do list. I think we should fail the materialization job if the feature view have multiple sort keys or non numeric types
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Materialization changes for Redis range query use cases
Design:
https://expediagroup.atlassian.net/wiki/spaces/PE/pages/438055297
Issue:
https://expediagroup.atlassian.net/browse/EAPC-20219
https://expediagroup.atlassian.net/browse/EAPC-20272