Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-20305

Pagination w/ Server Side Range Queries

    XMLWordPrintableJSON

Details

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Querying
    • None
    • Query Optimization

    Description

      The .min() and .max() features are nice but require specifying min or max values for all fields in the index. This makes it difficult to mix and match sort orders. Additionally, it would be beneficial to be able to specify some fields from the index in the search criteria (using $all or $in) and the remainder of the criteria in the .min() or .max() or in a new potential method such as.getNextPage().

      If such a feature as getNextPage() (or a better name) were available, the customer would pass in just enough sorting information such that combined with the standard search criteria, the system could pick up where the previous query left off. More specifically, the customer would pass in the partial sort values from the last document of the previous result set. The system in return would transform these values into additional search criteria.

      Documentation and examples attached.

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            christopher.price@mtvn.com Christopher Price
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: