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

Remove HostTypeRequirement::kPrimaryShard from $out

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • Fully Compatible
    • QE 2023-11-27, QE 2023-12-11, QE 2023-12-25, QE 2024-01-08, QE 2024-01-22, QE 2024-02-05, QE 2024-02-19

      • Implement distributedPlanLogic() to select the shard on which we are writing the data indicate that the merging pipeline (or full pipeline if unsplit) should be executed on that shard.
      • That ShardId should be stored as a data member and passed to MongoProcessInterface::createCollection() when creating the temp collection.

      Test cases:

      • Input and output collection both exist, are both unsharded and both reside on the same non-primary shard
      • Input and output collection both exist and are unsharded but reside on different non-primary shards
      • Input collection is sharded. Output collection exists and resides on a non-primary shard.
      • Output collection does not exist. Input collection is unsharded and resides on a non-primary shard.
      • Output collection exist and resides on a non-primary shard and moved during execution to another shard.

            Assignee:
            mihai.andrei@mongodb.com Mihai Andrei
            Reporter:
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: