[DOCS-9026] Regression of "mongodump --collection" Usage from 2.0.x to 2.2.x Created: 28/Sep/16  Updated: 30/Oct/23  Resolved: 14/Feb/17

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Emily Hall Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-7721 Regression of "mongodump --collection... Closed
Participants:
Days since reply: 7 years, 20 weeks ago

 Description   

Using mongo v2.0.8, I created two collections, a.counter and b.counter, and then ran mongodump v2.0.8 w/o specifying a database. The observed behavior is mongodump iterating through all databases and looks for the "counter" collection.

/tmp> /opt/mongodb-osx-x86_64-2.0.8/bin/mongodump --port 12345 -c counter
connected to: 127.0.0.1:12345
all dbs
DATABASE: a	 to 	dump/a
	a.counter to dump/a/counter.bson
		 1000 objects
DATABASE: b	 to 	dump/b
	b.counter to dump/b/counter.bson
		 1000 objects
DATABASE: *	 to 	dump/*

mongodump v2.2.1 results in:

/tmp> /opt/mongodb-osx-x86_64-2.2.1/bin/mongodump --port 12345 -c counter
connected to: 127.0.0.1:12345
Tue Nov 20 10:25:16 all dbs
assertion: 13106 nextSafe(): { $err: "db name can't be empty", code: 13075 }

This seems like a regression, or at minimum, an undocumented change in behavior.


Generated at Thu Feb 08 07:57:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.