Handle nested shard key fields in ShardVersionMap construction

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • ALL
    • Sharding 2020-09-07
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Shard keys containing dotted fields are not properly handled when constructing the ShardVersionMap: the [Min|Max]Key check function is only expecting a non-nested object potentially leading to ConflictingOperationError.

       

      That's an example of error raised following a refine shard key with nested fields:

      "error":"ConflictingOperationInProgress: Not all elements of { a: MinKey, b: { c: MinKey } } are of type minKey"
      

              Assignee:
              Pierlauro Sciarelli
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: