Remove deprecated zset lex (#3328) #3602
Open
+0
−57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR follows up on the existing Sorted Set API cleanup discussions in #363 and the follow-up in #3328.
It removes deprecated lex-based ZSET overloads that accept
String min/maxparameters and consolidates lexicographical range operations around theRange/LimitAPI.Changes
RedisSortedSetCommands:zlexcount(K, String, String)zrangebylex(K, String, String)zrangebylex(K, String, String, long, long)zremrangebylex(K, String, String)Range/Limit-based lex operations while preserving boundary semanticsMotivation
These deprecated overloads duplicate existing
Range/Limit-based APIs and increase the surface area of the public API. Removing them improves consistency, reduces maintenance overhead, and aligns with the ongoing Sorted Set API cleanup planned for the next major release.Refs: #363, #3328