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

Server allows renaming a “normal” collection to be system.buckets.

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 5.3.2, 6.0.6
    • Component/s: None
    • Storage Execution
    • ALL
    • Hide 
      replset [direct: primary] test> db.createCollection("mongosync.tmp.haha")
{ ok: 1 }
replset [direct: primary] test> db.mongosync.tmp.haha.renameCollection("system.buckets.haha")
{ ok: 1 }
replset [direct: primary] test> show tables
system.buckets.haha
system.views
      Show
      replset [direct: primary] test> db.createCollection( "mongosync.tmp.haha" ) { ok: 1 } replset [direct: primary] test> db.mongosync.tmp.haha.renameCollection( "system.buckets.haha" ) { ok: 1 } replset [direct: primary] test> show tables system.buckets.haha system.views

      The server seems to allow renaming into a system.buckets. collection name. This should probably be forbidden since there’s no good reason for it (and several bad ones).

      I had hoped that this would obviate SERVER-77003, but since this wouldn’t allow the `timeseries` options that are needed for proper creation of system.buckets collections, we still need SERVER-77003.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            felipe.gasper@mongodb.com Felipe Gasper
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: