Elevate $mergeCursors/AsyncResultsMerger missing $sortKey to tassert

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the ARM will return an error status when a reply from a shard does not contain a $sortKey. This results in a DocumentSourceMergeCursors triggering a uassert here.

      A shard returning a document without a $sortKey when the merging node was expecting one represents a bug in the query planner/engine. Raising this error condition as a tassert will allow our AF infrastructure to capture this failure and find bugs like SERVER-103724.

            Assignee:
            Unassigned
            Reporter:
            Ben Shteinfeld
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: