[SERVER-76580] Allow overriding SerializationContext objs constructed in IDL Created: 26/Apr/23 Updated: 29/Oct/23 Resolved: 28/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Hugh Tong (Inactive) | Assignee: | Hugh Tong (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Server Serverless 2023-05-01 | ||||||||
| Participants: | |||||||||
| Description |
|
When the parse(IDLParserContext&, BSONObj&) method is called, we automatically assume this is a command request and construct the serialization context accordingly. However, this method can also be called when building oplog entries, so we need to be able to override the default serialization context being constructed in parse() by passing a non-default one in via the IDLParserContext. This currently affects importCollection and collMod. As the goal of these changes are in pursuit of fixing tests that will fail once serializeForCommands and deserializeForCommands are plumbed in, no new tests are being added for this ticket. |
| Comments |
| Comment by Githook User [ 28/Apr/23 ] |
|
Author: {'name': 'Hugh Tong', 'email': 'hugh.tong@mongodb.com', 'username': 'cortrain'}Message: |