[DOCS-12015] Docs for SERVER-36424: Make sure $out's uniqueKey is unique when target collection is unsharded Created: 04/Sep/18  Updated: 13/Nov/23  Resolved: 01/Oct/18

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.3, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-36424 Make sure $out's uniqueKey is unique ... Closed
Related
related to DOCS-12028 New syntax for $out aggregation stage Closed
Participants:
Days since reply: 5 years, 23 weeks, 1 day ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

See the design or the tests for details - in order to use a uniqueKey other than the default you have to be sure there is a compatible unique index. 'compatible' is a bit complicated to define, so I won't attempt to do it again in this box.

Engineering Ticket Description:

This is just the unsharded piece of SERVER-36047, which we can split off because it won't depend on support for $out to a sharded collection in the same way.

As part of this ticket we should verify that:

  1. An index exists with some combination of the fields from the uniqueKey. The order of the uniqueKey fields shouldn't matter here, so if my uniqueKey was {a: 1, b: 1} an index on {b: 1, a: 1} should suffice.
  2. That index is unique.
  3. That index is not partial.
  4. That index is compatible with the operation's collation.

 

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


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