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

mongos does not appropriately emulate mongod when db does not exist in aggregation commands

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Query Execution
    • QE 2024-04-01, QE 2024-04-15, QE 2024-04-29, QE 2024-05-13

      In order to get a response closest to a replSet we should try sending the command directly to a random shard.
      We need to create our own CollectionRoutingInfo with shardVersion UNSHARDED and dbVersion with timestamp zero. this will ensure the command is properly retried if the collection is concurrently created.
      collections with foreign namespaces (ie there is a $out, $merge, $lookup, $unionWith, ect) should not be eligible for this option immediately so those can still return an empty batch for now, we will consider these stages in a follow up ticket.

            Assignee:
            kristina.znam@mongodb.com Kristina Znam
            Reporter:
            mickey.winters@mongodb.com Mickey Winters
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: