Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-79549

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

    • Catalog and Routing
    • 2

      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:
            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: