Uploaded image for project: 'Geode'
  1. Geode
  2. GEODE-9391

Implement LIMIT Option on Supported Commands

Agile BoardRank to TopRank to BottomAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.15.0
    • Component/s: redis
    • Labels:

      Description

      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.

        Attachments

        Issue Links

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              donalevans Donal Evans
              Reporter:
              wmilsted_vm Wayne

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment