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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.4.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      .. 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.

              Assignee:
              Unassigned
              Reporter:
              Greg Studer (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: