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

`isRangeEntirelyOwned` must provide an option to include/exclude the max key

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2024-03-18
    • 1

      ScopedCollectionFilter::isRangeEntirelyOwned is using getShardIdsForRange that includes the max bound when looking for overlapping chunks.

      However, all current usages of isRangeEntirelyOwned are meant to know if a [min, max) range is owned rather than [min, max]. Purpose of this ticket is to add a flag to the method in order to specify whether the max bound should be included or not.

            Assignee:
            enrico.golfieri@mongodb.com Enrico Golfieri
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: