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

Inconsistent metadata validation for $sample pipelines

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

      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 Unassigned
            Reporter:
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: