[SERVER-33325] review use of "b" field in applyOps update operations in sharding_catalog_manager_chunk_operations.cpp Created: 14/Feb/18 Updated: 09/Jun/22 Resolved: 30/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | pm-564 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding EMEA 2022-06-13 | ||||||||
| Participants: | |||||||||
| Description |
|
Some of the chunk operations rely on the applyOps command. Some of the generated update operations still set the b field to enable upserts. Setting the b field has no effect unless the alwaysUpsert option is set to false; " We should review the use of the b field in this code and remove it/replace the update with an insert where it is appropriate. |
| Comments |
| Comment by Marcos José Grillo Ramirez [ 30/May/22 ] |
|
This was addressed by the changes on SERVER-33326. |
| Comment by Kaloian Manassiev [ 15/Feb/18 ] |
|
Unless there is more pressing reason to remove the 'b' field, I would prefer to block this ticket as dependent on |