[SERVER-65859] Enable filtering of change steam events for individual statements of transactions Created: 21/Apr/22  Updated: 29/Oct/23  Resolved: 16/May/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc6, 6.1.0-rc0

Type: Task Priority: Blocker - P1
Reporter: Antonio Fuschetto Assignee: Andrii Dobroshynski (Inactive)
Resolution: Fixed Votes: 0
Labels: pm1950-m6
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-66312 Tests on batched operations do not in... Closed
depends on SERVER-65858 Mark the applyOps entries when the op... Closed
is depended on by SERVER-64107 Clean up orphaned doc handling in the... Closed
is depended on by SERVER-65295 Handle direct CRUD ops to shards as p... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Sprint: QE 2022-05-16
Participants:

 Description   

The full picture of problem and solution is described here.

The applyOps entries will be extended by the Sharding EMEA team with the fromMigrate flag and set it when the operations involve orphaned documents.

The goal of this ticket is to modify the filtering as necessary across change streams to filter out these entries.



 Comments   
Comment by Githook User [ 16/May/22 ]

Author:

{'name': 'Kyle Suarez', 'email': 'kyle.suarez@mongodb.com', 'username': 'ksuarz'}

Message: SERVER-65859 Enable filtering of 'fromMigrate' change steam events for individual operations within applyOps array
Branch: v6.0
https://github.com/mongodb/mongo/commit/5cc18bcd682fc59cd3714800a69f34246049caee

Comment by Githook User [ 15/May/22 ]

Author:

{'name': 'Andrii Dobroshynski', 'email': 'andrii.dobroshynski@mongodb.com'}

Message: SERVER-65859 Enable filtering of 'fromMigrate' change steam events for individual operations within applyOps array
Branch: master
https://github.com/mongodb/mongo/commit/4f68039a27c42a993454f701263b9a5d05720b0a

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