[DOCS-15036] [Server] Investigate changes in SERVER-58865: Remove obsolete restriction on capped collection objects Created: 13/Jan/22 Updated: 13/Nov/23 Resolved: 27/Jan/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 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: | Ian Fogelman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 2 years, 2 weeks, 1 day ago | ||||||||
| Description |
|
Downstream Change Summary This section needs to be updated: https://docs.mongodb.com/manual/core/capped-collections/#document-size Description of Linked TicketThe documentation for CannotGrowDocumentInCappedNamespace only uses MMAP as a motivation for having the error. MMAP has been removed for a few years now. We should consider coming up with a new reason that error must be returned (removing the reference to MMAP) or grapple with our FUD and remove the restriction altogether. |
| Comments |
| Comment by Githook User [ 25/Jan/22 ] |
|
Author: {'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}Message: |
| Comment by PM Bot [ 13/Jan/22 ] |
|
Downstream changes updated for upstream https://docs.mongodb.com/manual/core/capped-collections/#document-size |