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

Handle nested shard key fields in ShardVersionMap construction

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • ALL
    • Sharding 2020-09-07
    • 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@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None