-
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
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
- is caused by
-
-
- Closed
-
- is documented by
-
DOCS-13088 Note regarding Timestamp expansion is not accurate
-
- Resolved
-
- related to
-
SERVER-13695 Support $currentDate expression for insert
-
- Open
-