[SERVER-6961] v2.2 mongodump is incompatible with pre-v2.2 mongorestore Created: 06/Sep/12 Updated: 11/Jul/16 Resolved: 29/Oct/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.3.1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Shaun Verch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
mongodump's file layout is different in v2.2 than in v2.0 in a way that will lead to undesirable results if somebody happens to run a v2.0 mongorestore on a v2.2 mongodump layout. In particular, the new mongodump doesn't produce a system.indexes.bson for each database, and old mongorestore doesn't know what to do with the <collection>.metadata.json, so restoring with an old mongorestore will not retain indexes that existed in the dumped database. If we want to call this a regression, then a fix would be to have mongodump additionally create the system.indexes.bson file. Alternatively we could call this a documentation bug and update the release notes. |
| Comments |
| Comment by auto [ 29/Oct/12 ] |
|
Author: {u'date': u'2012-10-16T18:24:37-07:00', u'email': u'shaun.verch@10gen.com', u'name': u'Shaun Verch'}Message: |
| Comment by auto [ 13/Sep/12 ] |
|
Author: {u'date': u'2012-09-12T14:23:56-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}Message: |
| Comment by auto [ 13/Sep/12 ] |
|
Author: {u'date': u'2012-09-12T14:21:22-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}Message: |
| Comment by auto [ 13/Sep/12 ] |
|
Author: {u'date': u'2012-09-12T12:59:13-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}Message: |