-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Missing pipeline support for async ClusterClient #2186
Comments
Oh I thought this is not for the clustered version, which would include mapping commands within a pipeline to different nodes/shards, etc. |
@karwinliu You're right, I was looking at the async standalone client. Sorry, it looks like the async RedisCluster client inherits the |
No worries, would the pipeline be added soon? I think @utkarshgupta137 might already be working on it. I guess I'll just wait until it is ready |
I've got it working but I've only done basic testing. I will raise a PR once I write tests for it. If you want, you can check it out here: https://github.com/utkarshgupta137/redis-py/tree/async_cluster_pipeline |
Thanks @utkarshgupta137 for all the implementations. We've started to fully evaluate the async cluster, and it's been working well so far. But we do found some issues after using it extensively, and I have just submitted the issues. Would you mind taking a look? We have applied some simple patches to fix the issue locally, but ideally this could be fixed in the package soon. |
Hey, I've already raised a PR for the first 2 issues, one of which is merged & other should be merged before the next release. For 3rd, I'll have to check if it is possible to use the same command for slots across keys. |
Version: redis-py (4.3.1) redis server (6.0)
Platform: Python 3.9 on macOS Apple silicon
Description: I don't see the support of pipeline for the async cluster client. Besides, I don't find any documentation on async version of the cluster client, so maybe it's already implemented and can be invoked in some special ways. If not, I wonder if there's already a plan to support that and if there's any workaround for the time being.
The text was updated successfully, but these errors were encountered: