[SERVER-46341] unrecognized field 'useNewUpsert' Created: 24/Feb/20  Updated: 14/Mar/23  Resolved: 24/Feb/20

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: 4.2.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Marcos Fernándex Assignee: Eric Sedor
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-74794 PeriodicShardedIndexConsistencyChecke... Closed
Operating System: ALL
Participants:

 Description   

I just created a sharded cluster (no upgrade, all new) with mongo version: 4.2.3

Then went to make an aggregate as usual and found the following error:

Error: command failed: {
	"ok" : 0,
	"errmsg" : "unrecognized field 'useNewUpsert'",
	"code" : 9,
	"codeName" : "FailedToParse",
	"operationTime" : Timestamp(1582558484, 1),
	"$clusterTime" : {
		"clusterTime" : Timestamp(1582558484, 1),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
} : aggregate failed 

The  aggregate code is very simple:

db.getCollection('sigma').aggregate([
    {"$limit": 100}
])

Im unable to find any information about this field or how to disable it. Its referenced inside github mongo code and this is the only result in google I can find. Find commands works ok, aggregate is failing in php driver, robomongo and the mongo shell.



 Comments   
Comment by Eric Sedor [ 24/Feb/20 ]

Hi sombra2eternity@gmail.com,

No worries, and thanks for updating with what you found. I'll go ahead and close this.

Gratefully,
Eric

Comment by Marcos Fernándex [ 24/Feb/20 ]

Hmm after a deep revision of all shards I found one of them was in a lower version. Sorry for the noise, but this report may help people with this same error. Im searching the way to close this issue.

Generated at Thu Feb 08 05:11:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.