-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
ALL
-
Sometimes, the oplog contains a document that is not in the same order that it is eventually stored in. For some replace events, the _id field is last in the oplog, but when it's saved to disk, the document is reordered so that the _id field is first.
Max, in Slack, suggests that the update subsystem generates the oplog entry from the replacement as the client specified and not the change the update execution does.
Because this affects the change stream in fullDocument mode, we had to work around this in mongosync's application code by adjusting the document to move the _id field first. We would like to remove this workaround!