[DOCS-12052] Docs for SERVER-36367: Add validation checks for $out uniqueKey Created: 12/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-36367 Add validation checks for $out uniqueKey Closed
Related
related to DOCS-12028 New syntax for $out aggregation stage Closed
Participants:
Days since reply: 5 years, 22 weeks ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

This is just part of the broader $out project. The restrictions on the uniqueKey imposed by these code changes are like the description says:

In the "uniqueKey" spec:

  • no duplicate keys
  • no nested objects (use the dotted "nested.field" syntax instead)
  • all fields must have value 1

At runtime:

  • Each document must have every field of the uniqueKey. No fields of the uniqueKey may be missing, null, undefined or an array.

Engineering Ticket Description:

  • Duplicate keys
  • No nested objects
  • All fields must have value '1'
  • None of the values may be nullush

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:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.