Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Fully Compatible
-
Query 2018-08-13, Query 2018-08-27, Query 2018-09-10
Description
If the aggregation is run in a cluster, the unique key should be the _id and all of the fields of the shard key. Otherwise, the unique key is just the _id.
Attachments
Issue Links
- depends on
-
SERVER-35893 Update $out to accept new syntax
-
- Closed
-
- is depended on by
-
SERVER-18027 Support aggregation $out to sharded collection
-
- Closed
-
-
SERVER-36047 (Sharded target collection) Enforce existence of unique index containing fields of $out uniqueKey
-
- Closed
-
-
SERVER-36367 Add validation checks for $out uniqueKey
-
- Closed
-
-
SERVER-36813 Test the defaulting of uniqueKey when the catalog cache is stale
-
- Closed
-
- is documented by
-
DOCS-12018 Docs for SERVER-35954: Build uniqueKey from the shard key if not present in user command
-
- Closed
-