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

the E11000 duplicate key error looks different on each storage engine

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: MMAPv1, Storage
    • None
    • Storage Execution
    • ALL

      The ouput message for the 11000 should be the same regardless of the storage engine, but it is implemented different on each storage engine. For example:

      ephemeralForTest:

      "errmsg" : "E11000 duplicate key error dup key: { : 1.0 }",
      "op" : {
      	"_id" : ObjectId("5aa6ae9c39ecb419fc039661"),
      	"user_id" : 1
      }

      WiredTiger:

      "errmsg" : "E11000 duplicate key error collection: test.some_col index: user_id_1 dup key: { : 1.0 }",
      "op" : {
      	"_id" : ObjectId("5aa6b0f328382ba2890dc449"),
      	"user_id" : 1
      }

      mmapv1:

      "errmsg" : "E11000 duplicate key error index: test.some_col.$user_id_1 dup key: { : 1.0 }",
      "op" : {
      	"_id" : ObjectId("5aa6b12826491c753448b588"),
      	"user_id" : 1
      }

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            miguel.nieto@mongodb.com Miguel Ángel Nieto
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: