Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-7721

Regression of "mongodump --collection" Usage from 2.0.x to 2.2.x

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 2.3.2
    • Component/s: Tools
    • Labels:
      None
    • Backwards Compatibility:
      Major Change
    • Operating System:
      ALL
    • Steps To Reproduce:
      1. Create a v2.0.8 mongod standalone instance
      2. Populate two databases with the same collection name.
      3. mongodump v2.0.8 and mongodump v2.2.1.

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: