-
Type: Bug
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: 3.0.7, 3.2.0-rc0
-
Component/s: mongorestore
-
None
-
1
-
1,919
-
v3.2, v3.0
Running --oplogReplay on a single .bson file results in
~/Mongo $./mongodb-3.2.0-rc0/bin/mongorestore --oplogReplay dump/test/restaurants.bson 2015-10-21T17:43:12.227-0400 checking for collection data in dump/test/restaurants.bson 2015-10-21T17:43:12.228-0400 reading metadata for test.restaurants from 2015-10-21T17:43:12.229-0400 restoring test.restaurants from 2015-10-21T17:43:13.122-0400 restoring indexes for collection test.restaurants from metadata 2015-10-21T17:43:13.123-0400 finished restoring test.restaurants (25359 documents) 2015-10-21T17:43:13.124-0400 replaying oplog 2015-10-21T17:43:13.124-0400 no oplog.bson file in root of the dump directory, skipping oplog application 2015-10-21T17:43:13.124-0400 done
Mongorestore should not run the restore in this instance--we need to detect this and stop with a helpful error message.