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

allow aggregation to take an 'allowPartialResults' option

    • Type: Icon: New Feature New Feature
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.0-rc1
    • Component/s: Querying
    • Query Optimization

      The infrastructure for this is already in place: it's just a matter of parsing an 'allowPartialResults' option (similar to the find command) and passing it down to establishCursors(), which takes 'allowPartialResults' as a standalone boolean argument that the agg code currently always sets to false.

      We should also first double-check that it makes sense to accept allowPartialResults for all aggregations ($facet? $lookup? $graphLookup?).

      SERVER-28874 fixed the behavior of 'allowPartialResults' in establishCursors() and added thorough unit testing. It also added a jstest, jstests/sharding/allow_partial_results.js, which explicitly checks that aggregation does not accept the 'allowPartialResults' option, so this ticket should update that test.

            Assignee:
            backlog-query-optimization [DO NOT USE] Backlog - Query Optimization
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: