[SERVER-5734] mongodump shouldn't export config database by default Created: 01/May/12 Updated: 09/Jul/16 Resolved: 01/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.0.0, 2.1.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Remon van Vliet | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | dump, export | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently the mongodump tool exports the config database by default which is in the way of the standard dump -> restore flow. It seems very unlikely people would want to restore a config database by default, if only because it's extremely risky. Suggest not exporting it by default and add a flag to mongodump to include it if required. Alternatively a parameter to pass a list of databases that shouldn't be exported. |
| Comments |
| Comment by Remon van Vliet [ 01/May/12 ] |
|
Sorry, couldn't find a related issue. |
| Comment by Scott Hernandez (Inactive) [ 01/May/12 ] |
|
dup of |