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

Don't use $setUnion in aggregation for finding inconsistent sharded indexes

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.6, 4.4.0-rc0, 4.7.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • Sharding 2020-02-24, Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06

      The aggregation added in SERVER-44916 and used in SERVER-45389 to find inconsistent sharded indexes relies on $setUnion providing a consistent ordering, which is not supported. Instead, the pipeline will only consider fields known to be important, like name, key, and expireAfterSeconds untilĀ SERVER-29425 adds a supported way to sort an array.

            Assignee:
            jack.mulrow@mongodb.com Jack Mulrow
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: