[SERVER-36367] Add validation checks for $out uniqueKey Created: 30/Jul/18  Updated: 29/Oct/23  Resolved: 11/Sep/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: Kyle Suarez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-35954 Build uniqueKey from the shard key if... Closed
Documented
is documented by DOCS-12052 Docs for SERVER-36367: Add validation... Closed
Backwards Compatibility: Major Change
Sprint: Query 2018-09-10, Query 2018-09-24
Participants:

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


 Comments   
Comment by Githook User [ 11/Sep/18 ]

Author:

{'name': 'Kyle Suarez', 'email': 'kyle.suarez@mongodb.com', 'username': 'ksuarz'}

Message: SERVER-36367 validation for $out "uniqueKey"
Branch: master
https://github.com/mongodb/mongo/commit/602bc97e78d99d22d7ae6b867b6e92f5e2e279ca

Comment by Kyle Suarez [ 06/Sep/18 ]

Going to start typing on this right away since it should be more straightforward than the readConcern level "majority" ticket.

Comment by Nicholas Zolnierz [ 01/Aug/18 ]

charlie.swanson yep that makes sense to me.

Comment by Charlie Swanson [ 01/Aug/18 ]

kyle.suarez & nicholas.zolnierz after our discussion this morning in the design review, should this ticket also track the work to enforce that none of the uniqueKey fields are nullish?

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