[
https://issues.apache.org/jira/browse/GEODE-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans resolved GEODE-9391.
--------------------------------
Fix Version/s: 1.15.0
Resolution: Fixed
The individual RANGE commands each implemented the LIMIT option when they were
done, so this ticket was resolved when the last of them was merged.
> Implement LIMIT Option on Supported Commands
> --------------------------------------------
>
> Key: GEODE-9391
> URL: https://issues.apache.org/jira/browse/GEODE-9391
> Project: Geode
> Issue Type: New Feature
> Components: redis
> Reporter: Wayne
> Assignee: Donal Evans
> Priority: Major
> Labels: redis
> Fix For: 1.15.0
>
>
> Implement the LIMIT option on ZRANGE, ZREVRANGE, ZRANGEBYSCORE,
> ZREVRANGEBYSCORE, ZRANGEBYLEX, and XREVRANGEBYLEX.
>
> The optional LIMIT argument can be used to obtain a sub-range from the
> matching elements (similar to _SELECT LIMIT offset, count_ in SQL). A
> negative <count> returns all elements from the <offset>. Keep in mind that if
> <offset> is large, the sorted set needs to be traversed for <offset>elements
> before getting to the elements to return, which can add up to O(N) time
> complexity.
> +Acceptance Criteria+
> The LIMIT option has been implemented on the above commands and appropriate
> unit tests developed. The redis-cli was used to ensure the LIMIT command
> option works correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
