-
Notifications
You must be signed in to change notification settings - Fork 348
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
[FEATURE] Add support for Redis Functions #514
Comments
Thanks for your suggestion! I'll try to add built-in support for Redis Function. B.T.W. Before that feature is ready, you can use the generic interface to send commands related to Redis Function:
Regards |
@sewenew thank you for looking at this! We tried the generic command interface, but there's a problem! The command interface is treating the first argument to .command as the key. This is a problem in Redis Cluster configurations because our FCALL command calls are being routed to the wrong node/slot. For example This command will (almost) always fail, because it's using "authorize_player_join" as the key, instead of the third argument. So, we always get sent to the same (incorrect) Redis host. |
You can use the NOTE: In order to improve performance, you should set Regards |
Do you have any updates on this? 🙈 |
@ivantishchenko Sorry, but there's no progress on this topic. Too busy these days, I'll try it when I'm available. I'll let you know when there's progress. Regards |
#598 supports Redis function. |
Is your feature request related to a problem? Please describe.
We use Redis Functions to perform atomic R+W operations in a more ergonomic way than the evalsha API.
Describe the solution you'd like
The ability to use redis fcall in redis-plus-plus
Describe alternatives you've considered
Transactions, evalsha, and calling out to a separate component with Redis function support
Additional context
Thank you so much for making this library!
The text was updated successfully, but these errors were encountered: