dropDatabase not removing folders with wiredTiger

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Minor - P4
    • None
    • Affects Version/s: 3.0.0
    • Component/s: WiredTiger
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When doing a dropDatabase() using MMAPv1 on versions from 2.4 -> 3.0.1, the relevant folders which contain the data when using directoryPerDB: true are also removed.

      However, when performing the same dropDatabase using the wiredTiger engine and directoryPerDB: true, the directories are left in-tact, and only the related files are removed.

      (note, only tested with directoryForIndexes: true in 3.0.1)

              Assignee:
              Unassigned
              Reporter:
              Chad Kreimendahl
              Votes:
              1 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: