Core Server
  1. Core Server
  2. SERVER-4302

user shouldn't be able to create collection having a name prefixed by 'system.'

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major - P3 Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Planning Bucket A
    • Component/s: Storage
    • Labels:
      None
    • Backport:
      No
    • Operating System:
      ALL
    • # Replies:
      2
    • Last comment by Customer:
      false

      Description

      From Sridhar's email:

      This was from the field and I can reproduce it as follows

      I can use db.createCollection("system.foobar") to create a collection with the system prefix.

      I cannot seem to drop this collection since I get
      > db.system.foobar.drop()
      Wed Nov 16 16:30:11 uncaught exception: drop failed:

      { "ns" : "test.system.foobar", "errmsg" : "exception: can't drop system ns", "code" : 12502, "ok" : 0 }

      There is a check in pdfile.cpp in dropNS that checks for this

        Issue Links

          Activity

          Hide
          Chris Westin
          added a comment -

          Won't that mean I can't (indirectly) create system.profile by turning on the profiler? How about dropping and resizing system.profile (which is a capped collection)? Are there other 'system.' collections I might need to manipulate?

          Show
          Chris Westin
          added a comment - Won't that mean I can't (indirectly) create system.profile by turning on the profiler? How about dropping and resizing system.profile (which is a capped collection)? Are there other 'system.' collections I might need to manipulate?
          Hide
          Eliot Horowitz
          added a comment -

          Yes - there is already a list of approved ones and operations.

          Show
          Eliot Horowitz
          added a comment - Yes - there is already a list of approved ones and operations.

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Days since reply:
                2 years, 22 weeks, 6 days ago
                Date of 1st Reply: