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

scanAndOrder doesn't appear in profiler output in 2.5.x

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 2.5.5
    • Affects Version/s: 2.5.4
    • Component/s: Diagnostics, Querying
    • None

      db.setProfilingLevel(0)
      db.system.profile.drop()
      db.bar.drop();
      
      db.bar.insert( { "x" : 7, "r" : 0.999768219422549 } )
      db.bar.insert( { "x" : 92, "r" : 0.9881451367400587 } )
      db.bar.insert( { "x" : 45, "r" : 0.9833264029584825 } )
      
      // no indexes other than { _id: 1 } 
      
      db.setProfilingLevel(2)
      
      db.bar.find().sort( { r: -1 } )
      
      db.system.profile.find().sort( {$natural: 1} ).limit(1).pretty();
      

      In 2.4.x we see a document that has the scanAndOrder field which doesn't appear in 2.5.5-pre.

      Previously scanAndOrder only appeared when true, which is itself a bit odd.

            Assignee:
            david.storch@mongodb.com David Storch
            Reporter:
            sam.kleinman Sam Kleinman (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: