[SERVER-35954] Build uniqueKey from the shard key if not present in user command Created: 03/Jul/18  Updated: 29/Oct/23  Resolved: 24/Aug/18

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: 4.1.3

Type: Task Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Charlie Swanson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-35893 Update $out to accept new syntax Closed
is depended on by SERVER-18027 Support aggregation $out to sharded c... Closed
is depended on by SERVER-36047 (Sharded target collection) Enforce e... Closed
is depended on by SERVER-36367 Add validation checks for $out uniqueKey Closed
is depended on by SERVER-36813 Test the defaulting of uniqueKey when... Closed
Documented
is documented by DOCS-12018 Docs for SERVER-35954: Build uniqueKe... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2018-08-13, Query 2018-08-27, Query 2018-09-10
Participants:

 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.



 Comments   
Comment by Githook User [ 24/Aug/18 ]

Author:

{'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}

Message: SERVER-35954 Default uniqueKey to document key for sharded collection
Branch: master
https://github.com/mongodb/mongo/commit/375b524f3b8ee824ab7d9f52fd766b3af7fbbb80

Comment by Charlie Swanson [ 20/Aug/18 ]

Moving back to Open since I'm taking over the code review from Minji but not yet working on it. I'll drag it back to "In Code Review" once I open up a new review that I can add patches to.

Generated at Thu Feb 08 04:41:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.