-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In 6.1 we changed oplog format: SERVER-65909
In 7.1 we removed support for the old oplog format from change streams: SERVER-66138
In a very rare case that:
- A cluster is in the middle of upgrade from 7.0 to 8.0 where shard servers are on 8.0, but routers still on 7.0.
- A change stream is reading old oplog entries from 6.0.
- The router would include old oplog entries in the change stream filter.
- The shard server will fail the query because it won't be able to parse those oplog entries.
- is related to
-
SERVER-65909 Make oplog and change stream formats of {op: "n"} events consistent
-
- Closed
-
-
SERVER-66138 Remove support for 'o2.type' fields for no-op oplog entries in change streams code
-
- Closed
-