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

rollback via refetch assumes dropTarget field is always present

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.7.4
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2018-04-09
    • 89

    Description

      Before SERVER-34196, renameCollection oplog entries always contained a dropTarget field that would be set to either a boolean value or a collection UUID. Now the server will omit the dropTarget field if it doesn't drop any collections during the rename; if the dropTarget field is present, it must be a UUID.

      This does not apply to versions 3.6 and before.

      Attachments

        Activity

          People

            benety.goh@mongodb.com Benety Goh
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: