[SERVER-69804] Implement proper start/stop timestamp for configureQueryAnalyzer command Created: 19/Sep/22 Updated: 29/Oct/23 Resolved: 05/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Israel Hsu | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding NYC
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding NYC 2023-04-17 |
| Participants: |
| Description |
|
Currently, lastStartDate and lastStopDate of query analyzer settings document are updated only based on the mode ("full" or "off) of the command. If we really need these timestamps, the timestamps should only be updated if the actual state is changed by executing the command (i.e. no update if the mode is already "full" when the command specifies "full" mode). See `ConfigureQueryAnalyzerCmd::typedRun()` |
| Comments |
| Comment by Githook User [ 05/Apr/23 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |
| Comment by Githook User [ 04/Apr/23 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |