[SERVER-58348] Don't set curOp's networkop field to deprecated dbDelete and dbUpdate Created: 07/Jul/21 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Irina Yatsenko (Inactive) | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
When creating nested curOps for update and delete we currently set their networkop field to be dbUpdate and dbDelete respectively, even though the operations came in as commands (dbMsg). This is inconsistent with the networkop setting on other operations and has potential for confusion. Proposal: when creating nested curOp inherit the network op from the parent, use logicalop for logging if required to know the specific operation. |
| Comments |
| Comment by David Storch [ 09/Aug/21 ] |
|
I'm removing this from the legacy op codes deletion project. It is a minor code simplification that would be nice to do, but is not strictly required for the project. I'm putting this back into the "needs scheduling" queue, but I suggest putting it in the backlog with the "neweng" label. |