[SERVER-68784] Do not write no-op entries to change collections Created: 12/Aug/22  Updated: 13/Sep/22  Resolved: 13/Sep/22

Status: Closed
Project: Core Server
Component/s: Change streams
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Mindaugas Malinauskas Assignee: Rishab Joshi (Inactive)
Resolution: Won't Do Votes: 0
Labels: pm-2334-m2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: QE 2022-09-19
Participants:

 Description   

Do not write no-op entries to change collections. Currently, all oplog entries are written to change collection since full multi-tenancy support is not available yet. To simulate the ultimate behavior with regards to no-op entries (no-op entries are not copied to change collections) we might want to temporarily exclude writing of no-op entries to change collections.



 Comments   
Comment by Rishab Joshi (Inactive) [ 13/Sep/22 ]

This ticket is no longer required as we are able to pass tenant id to the change collection for a sharded cluster. This work is been done in SERVER-66641

Generated at Thu Feb 08 06:11:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.