-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 3.3.14
-
Component/s: mongodump
-
Platforms 2016-11-21
It looks like mongodump stopped reporting the number of dumped documents around 3.3.12 to 3.3.14 when a query is specified. The dump itself does contain the correct number of documents.
➜ dev.mongo git:(master) ✗ ../bin.mongo/3.3.11/mongodump -d db0 -c coll0 -q "{tid:40}" -o out
2016-10-26T18:55:53.833-0400 writing db0.coll0 to
2016-10-26T18:55:53.854-0400 done dumping db0.coll0 (682 documents)
➜ dev.mongo git:(master) ✗ ../bin.mongo/3.3.14/mongodump -d db0 -c coll0 -q "{tid:40}" -o out
2016-10-26T18:55:57.643-0400 writing db0.coll0 to
2016-10-26T18:55:57.662-0400 done dumping db0.coll0 (0 documents)
➜ dev.mongo git:(master) ✗ ../bin.mongo/3.3.14/mongodump -d db0 -c coll0 -o out
2016-10-26T18:56:02.063-0400 writing db0.coll0 to
2016-10-26T18:56:02.162-0400 done dumping db0.coll0 (33417 documents)
➜ dev.mongo git:(master) ✗ ../bin.mongo/3.3.11/mongodump -d db0 -c coll0 -o out
2016-10-26T18:56:07.111-0400 writing db0.coll0 to
2016-10-26T18:56:07.217-0400 done dumping db0.coll0 (33417 documents)