-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
The common oplog format for update operation is like this, has `o.$set` field:
{"ts":Timestamp(1521530692,1),"t":NumberLong("5"),"h":NumberLong("-384939294837368966"), "v":2,"op":"u","ns":"foo.bar","o2":{"_id":"L0KB$fjfLFra"},"o":{"$set":{"apns":"[]"}}}
but after some times (around 2.1M log entries now), there exists one log:
db.getCollection("oplog.rs").find({op: 'u', 'o.$set': { $exists: false}})
is this a bug?
