Inconsistent metadata validation for $sample pipelines

XMLWordPrintableJSON

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

      Noticed while working on $sample inside of $rankFusion that we are not consistent with how we validate this. In particular we at least have a problem where sharded queries will fail to error when they reference certain unpopulated metadata fields like "geoNearDistance".

      See the patch for SERVER-100360 for a TODO about this ticket.

              Assignee:
              Unassigned
              Reporter:
              Charlie Swanson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: