[SERVER-72806] Split produceNewDocumentForInsert into it's own class Created: 12/Jan/23 Updated: 29/Oct/23 Resolved: 18/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sanika Phanse (Inactive) | Assignee: | Sanika Phanse (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: | Sharding NYC 2023-01-23 | ||||||||
| Participants: | |||||||||
| Description |
|
In order to include the logic to produce a new document for insert without bringing the binary for any plan stages into mongos, split produceNewDocumentForInsert out from UpsertStage into its own class. This ticket is only responsible for creating the new class and integrating it with UpsertStage/UpdateStage. Using this new class in _clusterQueryWithoutShardKey will be handled in a separate ticket. |
| Comments |
| Comment by Githook User [ 18/Jan/23 ] |
|
Author: {'name': 'Sanika Phanse', 'email': 'sanika.phanse@mongodb.com', 'username': 'sphanse99'}Message: |