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

Mapreduce should not create collections with duplicate IDs

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.10
    • Affects Version/s: 3.6.9
    • Component/s: MapReduce
    • None
    • Fully Compatible
    • ALL
    • 45

      If a mapreduce is run while downgrading to compatibility version 3.4 (but before UUIDs are removed), and the final output collection exists, the new temporary collection will have the same UUID as the old final output collection. We should clear the options.uuid field whenever we do not set it explicitly.

            Assignee:
            matthew.russotto@mongodb.com Matthew Russotto
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: