[SERVER-12474] mongos gle no longer returns updatedExisting in 2.5.4 nightly Created: 24/Jan/14  Updated: 05/May/14  Resolved: 29/Jan/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.5.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Bernie Hackett Assignee: Greg Studer
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-12419 mongos GLE does not work correctly if... Closed
Related
related to SERVER-12404 err field can appear twice in getLast... Closed
related to SERVER-12274 Fail-fast on invalid WriteConcern opt... Closed
is related to SERVER-12329 UpdatedExisting always true after upd... Closed
Operating System: ALL
Participants:

 Description   

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
}


Generated at Thu Feb 08 03:28:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.