Translate UnknownError raised by checkShardingIndex to InvalidOptions error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.0-rc2
    • Affects Version/s: 8.0.0-rc1
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2024-04-15
    • 152
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      On SERVER-88548, we changed the behavior of checkShardingIndex command to throw an InvalidOptions error instead of returning an UnknownError, so that there was no need to translate it at the shardCollection operation level.

      However, in a multiversion scenario, we may still receive an UnknownError from a checkShardingIndex command running on an old binary node that has to be translated to an InvalidOptions error.

      So, we still need to translate an UnknownError to a InvalidOptions error until v8.0 becomes the last LTS (note that we will backport SERVER-88548 to v8.0 before it gets released).

            Assignee:
            Silvia Surroca
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: