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

Make sure $out's uniqueKey is unique when target collection is unsharded

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.1.3
    • Aggregation Framework
    • None
    • Fully Compatible
    • Query 2018-08-13, Query 2018-08-27, Query 2018-09-10

    Description

      This is just the unsharded piece of SERVER-36047, which we can split off because it won't depend on support for $out to a sharded collection in the same way.

      As part of this ticket we should verify that:

      1. An index exists with some combination of the fields from the uniqueKey. The order of the uniqueKey fields shouldn't matter here, so if my uniqueKey was {a: 1, b: 1} an index on {b: 1, a: 1} should suffice.
      2. That index is unique.
      3. That index is not partial.
      4. That index is compatible with the operation's collation.

       

      Attachments

        Issue Links

          Activity

            People

              charlie.swanson@mongodb.com Charlie Swanson
              charlie.swanson@mongodb.com Charlie Swanson
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: