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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 5.3.2, 6.0.6
    • Component/s: None
    • Catalog and Routing
    • 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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:
              Unassigned
              Reporter:
              Felipe Gasper
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: