[DOCS-5672] mongorestore with --drop option Created: 18/Jun/15 Updated: 24/Feb/16 Resolved: 22/Jun/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | mongodb-3.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 8 years, 34 weeks, 2 days ago |
| Description |
|
http://docs.mongodb.org/manual/reference/program/mongorestore/#cmdoption--drop The --drop option for mongorestore states "Modifies the restoration procedure to drop every collection from the target database before restoring the collection from the dumped backup." This should be reworded based on the current behavior. The --drop will not affect collections in the target database, if they are not in the dump. For example:
The collections c1 & c2 will be restored from the dump, but c3 will still exist with the documents. CC: mpobrien Please confirm this is the expected behavior. |
| Comments |
| Comment by Githook User [ 22/Jun/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 22/Jun/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 22/Jun/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |