[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: |
|
||||||||||||||||
| 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:
|
| Comments |
| Comment by Pierlauro Sciarelli [ 03/Sep/20 ] |
|
|