[DOCS-13205] Investigate changes in SERVER-44382: Allow upserting a document that is missing a shard key field Created: 06/Nov/19  Updated: 13/Nov/23  Resolved: 26/Feb/20

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

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-44382 Allow upserting a document that is mi... Closed
Duplicate
Gantt Dependency
Related
Participants:
Days since reply: 3 years, 50 weeks, 1 day ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

This ticket fixed a bug in SERVER-42390 that didn't allow upserted documents to have missing shard key fields. The behavior is the same as should have been communicated through SERVER-42390's downstream changes, I only gave this ticket downstream changes to make sure it's clear the bug wasn't the intentional behavior.

Description of Linked Ticket

SERVER-42390 allowed users to insert documents that are missing shard key fields and unset shard key fields through an update. An upsert that doesn't match an existing document takes a different code path than other updates, which currently incorrectly will reject a write that would result in a document without a shard key field because of this check. Instead, the upsert path should only assert the shard key paths do not contain arrays and that _id is present and does not contain an array.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Kay Kim (Inactive) [ 26/Feb/20 ]

The linked DOCSP-7020 is the docs ticket for the SERVER-42390 mentioned in the description.

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