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

$inc behaves differently for missing vs null fields

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Write Ops
    • Labels:
      None
    • Query Optimization

      We usually try to treat null and missing fields mostly the same, so this seems like surprising behavior.

      MongoDB Enterprise asdf:PRIMARY> db.foo.insert({_id: 1, b: null})
      WriteResult({ "nInserted" : 1 })
      MongoDB Enterprise asdf:PRIMARY> db.foo.update({_id: 1}, {$inc: {a: 1}})
      WriteResult({ "nMatched" : 1, "nUpserted" : 0, "nModified" : 1 })
      MongoDB Enterprise asdf:PRIMARY> db.foo.update({_id: 1}, {$inc: {b: 1}})
      WriteResult({
              "nMatched" : 0,
              "nUpserted" : 0,
              "nModified" : 0,
              "writeError" : {
                      "code" : 14,
                      "errmsg" : "Cannot apply $inc to a value of non-numeric type. {_id: 1.0} has the field 'b' of non-numeric type null"
              }
      })
      

            Assignee:
            backlog-query-optimization [DO NOT USE] Backlog - Query Optimization
            Reporter:
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: