The enableSharding command should correctly handle requests where the primary Shard ID is encoded as a connection string

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31
    • 35
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The enableSharding command accept an optional primaryShard parameter, which may represent either a Shard ID or a connection string.  While the the logic to add the entry to the catalog is able to support both encodings, some of the checks behave incorrectly when a connection string gets received

            Assignee:
            Paolo Polato
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: