[SERVER-23805] Use boost::optional to specify optional metrics in OpDebug Created: 19/Apr/16 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Diagnostics, Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
At present we use both '0' and '-1' to initialize OpDebug metrics. '-1' signifies unset but often introduces extra non-intuitive initialization work for users. '0' removes this work but makes understanding which metrics are unused harder. Use of boost:optional would make non-use explicit and make initialization / use clearer. |