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

Unable to do system.namespace collection counts with new storage enginers

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.8.0-rc2
    • Component/s: Storage
    • None
    • ALL
    • Hide

      with mmap this returns the number of collections on wired tiger as expected it returns nothing.

      > db.system.namespaces.find()

      { "name" : "b.system.indexes" } { "name" : "b.t.$_id_" } { "name" : "b.t" }

      > db.system.namespaces.find(

      {name: "b.t"}

      )

      { "name" : "b.t” }

      > db.system.namespaces.count(

      {name: "b.t"}

      )
      1

      Show
      with mmap this returns the number of collections on wired tiger as expected it returns nothing. > db.system.namespaces.find() { "name" : "b.system.indexes" } { "name" : "b.t.$_id_" } { "name" : "b.t" } > db.system.namespaces.find( {name: "b.t"} ) { "name" : "b.t” } > db.system.namespaces.count( {name: "b.t"} ) 1

      One of the things we cannot do after changing to use listCollections is to return counts of the number of collections for a given filter which we currently support in mmap.

      > db.system.namespaces.find()

      { "name" : "b.system.indexes" } { "name" : "b.t.$_id_" } { "name" : "b.t" }

      > db.system.namespaces.find(

      {name: "b.t"}

      )

      { "name" : "b.t” }

      > db.system.namespaces.count(

      {name: "b.t"}

      )
      1

            Assignee:
            Unassigned Unassigned
            Reporter:
            christkv Christian Amor Kvalheim
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: