[DOCS-10870] updateMany on a sharded cluster can be issued without specifying the shard key Created: 04/Oct/17  Updated: 30/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Kirby Kohlmorgen Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: crud, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.mongodb.com/v3.4/reference/method/db.collection.update/#sharded-collections


Issue Links:
Related
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769
Story Points: 0.3

 Description   

Currently, in our docs it states that:

All update() operations for a sharded collection must include the shard key or the _id field in the query specification. update() operations without the shard key or the _id field return an error.

This has led some of our students to believe that issuing an updateMany command would also require a shard key. This is not true. To address this confusion, could we do something like

With the exception of updateMany, all update() operations for a sharded collection must include the shard key or the _id field in the query specification. update() operations without the shard key or the _id field return an error.



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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