Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-12015

Docs for 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
    • manual, Server
    • None

    Description

      Description

      Description:

      See the design or the tests for details - in order to use a uniqueKey other than the default you have to be sure there is a compatible unique index. 'compatible' is a bit complicated to define, so I won't attempt to do it again in this box.

      Engineering Ticket 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.

       

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              kay.kim@mongodb.com Kay Kim (Inactive)
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                4 years, 3 weeks, 5 days ago