[SERVER-79549] Audit and perhaps consolidate the multiple implementations of ChunkRange::containsKey() Created: 31/Jul/23  Updated: 26/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-67529 Resharding silently skips documents w... Closed
Assigned Teams:
Catalog and Routing
Participants:
Story Points: 2

 Description   

The changes from b8e050a as part of SERVER-67529 changed the implementation of ChunkRange::containsKey() to support shard key values of the form {sk: MaxKey}. However, after some code inspection, it appears there are multiple functions defined separately from ChunkRange for comparing shard key values and are no longer consistent with the new definition of ChunkRange::containsKey(). Some examples of these other function definitions include:

Having multiple function definitions is problematic because it means some aspects of sharding may handle MaxKey appropriately and other aspects may not in a way which isn't predictable.


Generated at Thu Feb 08 06:41:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.