[SERVER-85253] Support extra fields and remove SerializationContext in building OpMsgRequest with ValidatedTenancyScope Created: 16/Jan/24  Updated: 19/Jan/24  Resolved: 19/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Sophia Tan Assignee: Sophia Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-84716 Make UMCTransaction build OpMsgReques... Closed
Issue split
split from SERVER-81825 Only support building OpMsgRequest wi... In Progress
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2024-01-22
Participants:
Story Points: 2

 Description   

Support extra fields when building OpMsgRequest with ValidatedTenancyScope.

The OpMsgRequest::createWithValidatedTenancyScope function should be changed to take in extraFields so that this function can be commonly used in more use cases which include extra fields.

As ValidatedTenancyScope is a source of creating SerializationContext,  this function need not to take in SerializationContext object. In this ticket, we can remove SerializationContext from the input params.



 Comments   
Comment by Githook User [ 19/Jan/24 ]

Author:

{'name': 'Sophia Tan', 'email': 'sophia_tll@hotmail.com', 'username': 'sophiatll'}

Message: SERVER-85253 Support extraFields and remove SerializationContext in building OpMsgRequest with ValidatedTenancyScope (#18129)

GitOrigin-RevId: d4f96aa184425fb7de914ae1683bf7487b622162
Branch: master
https://github.com/mongodb/mongo/commit/0d35120d1ac6162fae537c7886de58c166e8ded5

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