[SERVER-50627] Handle nested shard key fields in ShardVersionMap construction Created: 28/Aug/20  Updated: 27/Oct/23  Resolved: 04/Sep/20

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

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-50507 Avoid race conditions during recoverR... Closed
Related
is related to SERVER-50750 Refining shard key to include nested ... Closed
Operating System: ALL
Sprint: Sharding 2020-09-07
Participants:

 Description   

Shard keys containing dotted fields are not properly handled when constructing the ShardVersionMap: the [Min|Max]Key check function is only expecting a non-nested object potentially leading to ConflictingOperationError.

 

That's an example of error raised following a refine shard key with nested fields:

"error":"ConflictingOperationInProgress: Not all elements of { a: MinKey, b: { c: MinKey } } are of type minKey"



 Comments   
Comment by Pierlauro Sciarelli [ 03/Sep/20 ]

SERVER-50750 addresses a bug in the way refine shard key generates the new Min and Max keys and will solve the problem. Closing as "Works as Designed".

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