-
Notifications
You must be signed in to change notification settings - Fork 2.6k
4.0.0rc1 breaks various zrange commands on older servers #1669
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
Labels
bug
Bug
Comments
Thanks @bmerry for tracking this down all the way. We'll definitely get this into rc2! @AvitalFineRedis while we're here, let's test for this case. |
4 tasks
@chayim the following is still broken in 4.0.0rc2 (but worked in 3.5.3):
|
@AvitalFineRedis can you add a test with this specific case? Our 6.0.0 testing didn't seem to cover this. @bmerry thanks again, for highlighting this. |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Version: redis-py 4.0.0rc1, redis 6.0.16 (or any less than 6.2).
Platform: Python 3.8, Ubuntu 20.04
Description:
Previously calling
zrevrange
orzrange(..., desc=True)
would use ZREVRANGE on the wire. Somewhere between 4.0.0b1 and 4.0.0rc1 this changed to useZRANGE ... REV
, which is new syntax in Redis 6.2. When using an older server this causes a syntax error.To reproduce:
Other commands are also affected e.g. zrangebyscore and zrangebylex are also using ZRANGE with options on the wire which is not supported pre-6.2.
The text was updated successfully, but these errors were encountered: