[SERVER-70411] Serialize and deserialize DbCheckOplogBatch correctly Created: 10/Oct/22 Updated: 29/Oct/23 Resolved: 31/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Mathis Bessa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-10-31, Server Serverless 2022-11-14 |
| Participants: |
| Description |
|
We don't go through OpObserverImpl to write DbCheckOplogBatch entries, so we'll need to do this manually. Set the tid field on the oplog entry here. Then, pass the tenantId in the "tid" field to the IDLParserContext when parsing the entry here. |
| Comments |
| Comment by Githook User [ 31/Oct/22 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |