-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
QE 2024-02-19, QE 2024-03-04, QE 2024-03-18, QE 2024-04-01, QE 2024-04-15, QE 2024-04-29, QE 2024-05-13, QE 2024-05-27, QE 2024-06-10, QE 2024-06-24, QE 2024-07-08, QE 2024-07-22, QE 2024-08-05, QE 2024-08-19, QE 2024-09-02, QE 2024-09-16, QE 2024-09-30, QE 2024-10-14, QE 2024-10-28, QE 2024-11-11, QE 2024-11-25
After PM-1950, there are an increasing number of places where we write a no-op oplog message to signify to change streams that a particular event has occurred. Most of these places are now named notifyChangeStreamsOn* but are scattered throughout the code. We should make sure that ALL such no-op writers are named notifyChangeStreamsOn (e.g. the shardCollection no-op writer is currently just called _writeOplogMessage, the reshardBegin and reshardDoneCatchUp events are not in separate functions at all) and consolidate these into a dedicated library and API.