[SERVER-66604] Analyze command skeleton Created: 19/May/22 Updated: 29/Oct/23 Resolved: 11/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Joel Redman (Inactive) | Assignee: | Lynne Wang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | QO 2022-05-30, QO 2022-06-13, QO 2022-06-27, QO 2022-07-11, QO 2022-07-25 | ||||||||
| Participants: | |||||||||
| Description |
|
Create an analyze command matching the syntax in the scope document In this phase, the analyze command should result in a "Not Yet Implemented" error if the feature flag is enabled; otherwise, it should cause same error as if you had issued it today. |
| Comments |
| Comment by Githook User [ 06/Jul/22 ] |
|
Author: {'name': 'Lynne Wang', 'email': 'lynne.wang@mongodb.com'}Message: |
| Comment by Charlie Swanson [ 26/May/22 ] |
|
joel.redman@mongodb.com I see this is in an epic and assigned to you so I'm hitting "schedule" and putting it in the current sprint. |