[SERVER-69286] Populate top-level tenantId field in transactions more efficiently Created: 31/Aug/22  Updated: 01/Feb/24  Resolved: 01/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Hugh Tong (Inactive) Assignee: Backlog - Service Architecture
Resolution: Won't Do Votes: 0
Labels: ntdi_nice_to_have
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-86091 Complete TODO listed in SERVER-69286 Open
Assigned Teams:
Service Arch
Participants:
Story Points: 3

 Description   

When creating oplog entries for transactions, the top-level tenantId field needs to match the individual ops contained in the applyOps array.  SERVER-69233 represents a quick-fix that was needed to unblock SERVER-66641 which addressed this issue, but we may want to look at a more efficient way of populating the tenantId than parsing the BSONObj document.

The parsing is currently done in op_observer_impl.cpp, but we may wish to consider passing the tenantId down from commitTransaction/prepareTransaction calls instead.


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