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

Timestamp(0,0) not filled in for _id field

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Query 2019-10-07, Query 2019-10-21

      Description

      asdf:PRIMARY> db.foo.insert({_id: Timestamp(0,0)})
      WriteResult({ "nInserted" : 1 })
      asdf:PRIMARY> db.foo.insert({_id: 1, x: Timestamp(0,0)})
      WriteResult({ "nInserted" : 1 })
      asdf:PRIMARY> db.foo.insert({_id: 2, w: 1, x: Timestamp(0,0)})
      WriteResult({ "nInserted" : 1 })
      asdf:PRIMARY> db.foo.find()
      { "_id" : Timestamp(0, 0) }
      { "_id" : 1, "x" : Timestamp(1566529153, 1) }
      { "_id" : 2, "w" : 1, "x" : Timestamp(1566529173, 1) }
      

      The documentation says "Changed in version 2.6: Previously, the server would only replace empty timestamp values in the first two fields, including _id, of an inserted document. Now MongoDB will replace any top-level field." So either the server or the docs have a bug. https://docs.mongodb.com/manual/reference/bson-types/#timestamps

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              bernard.gorman Bernard Gorman
              Reporter:
              redbeard0531 Mathias Stearn
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: