[SERVER-70673] Revisit cmdObj creation in _clusterWriteWithoutShardKey and remove object if unnecessary. Created: 18/Oct/22 Updated: 16/Feb/23 Resolved: 16/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sanika Phanse (Inactive) | Assignee: | Jason Zhang |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | sharding-nyc-subteam3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding NYC 2022-11-14, Sharding NYC 2023-02-20 |
| Participants: |
| Description |
|
In the function `_createCmdObj` an extra command object is made such that $db can be appended and some fields are removed. Toy with unsetting the fields using the requestBuilder instead and reevaluate if setting $db is necessary. It might not be if it is always appended by update/delete/findAndModify commands or the transaction api before it is passed to _cluster(Query/Write)WithoutShardKey. |