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

dropDatabase silently fails after mapReduce in other connection

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 1.5.2
    • Affects Version/s: 1.3.3
    • Component/s: None
    • None
    • Environment:
      ubuntu 9.10, linux 32-bit build (1.3.3), java driver and mongo shell (1.3.3)

      After a mapReduce command has been performed in a database over one connection, an attempt to drop the same database in a second connection will silently fail. The command returns no error, but the database remains.

      To reproduce, use the mongo shell to create two connections.

      Connection1:
      1. use mydb
      2. db.items.save(

      {n:1}

      )
      3. res = db.items.mapReduce("function()

      { emit(1, 1); }

      ", "function(k,v) { var c=0; for(i in v)

      { c+= v[i]; }

      return c; }");
      4. db[res.result].find()

      Connection2:
      1. use mydb
      2. db.dropDatabase()

      Expect: Either an error message stating a decent reason why the database could not be deleted, or the database to go away.

      Actual: "show dbs" still lists "mydb"

            Assignee:
            richard.kreuter Richard Kreuter (Inactive)
            Reporter:
            steven.m.reed@gmail.com Steve Reed
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: