[DOCS-13098] Missing requirement for no collection renames during mongodump with --oplog Created: 13/Oct/19 Updated: 30/Oct/23 Resolved: 28/Jan/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, tools |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Sommer | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 4 years, 2 weeks, 1 day ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
DescriptionFor the mongodump –oplog option: https://docs.mongodb.com/manual/reference/program/mongodump/#cmdoption-mongodump-oplog In this code, mongodump will return an error if a collection rename has occurred. The requirement to ensure that collection renames don't occur if using --oplog appears to be missing from the documentation.
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 28/Jan/20 ] |
|
Going to use the more recent ticket to track this work. |