-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.5.4
-
Component/s: Sharding
-
None
-
ALL
Although we're moving to write commands there are likely applications in the wild relying on this.
MongoDB 2.4.9:
mongos> db.test.insert({i: 1}) mongos> db.test.update({i: 1}, {$set: {i: 1}}) mongos> db.runCommand('getLastError') { "singleShard" : "localhost:30000", "updatedExisting" : true, "n" : 1, "connectionId" : 2, "err" : null, "ok" : 1 }
MongoDB 2.5.4 nightly:
mongos> db.test.insert({i: 1}) ... mongos> db.test.update({i: 1}, {$set: {i: 1}}) ... "nUpdated" : 1, ... mongos> db.runCommand('getLastError') { "n" : 0, "shards" : [ ], "shardRawGLE" : { }, "err" : null, "ok" : 1 }
- duplicates
-
SERVER-12419 mongos GLE does not work correctly if previous write was from a command
- Closed
- is related to
-
SERVER-12329 UpdatedExisting always true after update command
- Closed
- related to
-
SERVER-12404 err field can appear twice in getLastError response
- Closed
-
SERVER-12274 Fail-fast on invalid WriteConcern options in write commands
- Closed