[DOCS-4840] Please update the write concern & bulk update docs to mention the purpose of bulk updates Created: 17/Feb/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | William Cross | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
I've got a few suggestions below; nothing urgent, and nothing in the docs is wrong. Currently, the write concern docs do not mention bulk updates, and the bulk docs don't mention the purpose, either. I would suggest adding a section to the write concern docs to say something like "If the overhead associated with getting acknowledgment for each write is a concern, you can amortize your write concern over up to 1,000 write operations is to use MongoDB's Bulk objects." I might also suggest, on the Bulk() page, leading with something similar, like "Bulk operations are used to amortize your write concern acknowledgment over up to 1,000 write operations at a time."
Hope the suggestions are useful! -Will |
| Comments |
| Comment by Education Bot [ 01/Nov/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! |