You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Owen Nichols (Jira)" <ji...@apache.org> on 2022/06/22 20:46:01 UTC

[jira] [Closed] (GEODE-9391) Implement LIMIT Option on Supported Commands

     [ https://issues.apache.org/jira/browse/GEODE-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen Nichols closed GEODE-9391.
-------------------------------

> 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.20.7#820007)