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

The check to reject a snapshot read on a sharded collection via the "distinct" command should happen on mongod not mongos

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • QE 2021-12-13, QE 2021-12-27, QE 2022-01-10, QE 2022-03-07, QE 2022-03-21, QE 2022-01-24

      This check can incorrectly reject a distinct command on an unsharded collection if there was a sharded collection that was dropped and recreated as unsharded.

      The check should instead be done on the shard using the shard's filtering metadata.

            Assignee:
            kyle.suarez@mongodb.com Kyle Suarez
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: