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

Correctly propagate new UUID for renaming across databases

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.5.10
    • None
    • Replication, Storage
    • None
    • Fully Compatible
    • ALL
    • Hide

      buildscripts/resmoke.py --suites=replica_sets_jscore_passthrough  "--mongodSetParameters={enableCollectionUUIDs: 1}" jstests/core/rename7.js
      

      Show
      buildscripts/resmoke.py --suites=replica_sets_jscore_passthrough "--mongodSetParameters={enableCollectionUUIDs: 1}" jstests/core/rename7.js
    • Storage 2017-07-10

    Description

      When enabling collection UUIDs, and renaming collections across databases, correctly pass through the UUID from the oplog entry, so primary and secondary will maintain identical UUIDs.

      Attachments

        Activity

          People

            geert.bosch@mongodb.com Geert Bosch
            geert.bosch@mongodb.com Geert Bosch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: