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

MapReduce should use dropTarget argument to rename rather than doing the drop itself

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • MapReduce
    • Query

    Description

      Having renameCollection do the dropping makes it more atomic by doing it in a single WriteUnitOfWork and generating a single oplog entry. Currently, it is possible for the drop to become durable or replicate without the rename. Also it is possible for a secondary reader to see the state between the drop and rename.

      Agg $out already uses dropTarget rather than an explicit drop.

      Attachments

        Activity

          People

            backlog-server-query Backlog - Query Team (Inactive)
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: