Audit and perhaps consolidate the multiple implementations of ChunkRange::containsKey()

XMLWordPrintableJSON

    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2024-10-28, CAR Team 2024-11-11, CAR Team 2024-11-25
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Igor Praznik
              Reporter:
              Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: