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

config upgrade v3 to v4 too paranoid about config.collection formats

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 2.4.0-rc0
    • None
    • None
    • None
    • ALL

    Description

      .. it's possible to get documents of the type:

      { _id : collName, lastmod : new Date(...), dropped : true }

      ...which are rejected by our parser as invalid before the upgrade can happen. We should modify the parser or the upgrade process to handle this case gracefully (by ignoring the collection).

      Workaround is to manually remove the dropped collection entry.

      Attachments

        Activity

          People

            Unassigned Unassigned
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: