[SERVER-67361] Extend analyze command to generate collection as needed Created: 17/Jun/22 Updated: 08/Jan/23 Resolved: 08/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Joel Redman (Inactive) | Assignee: | Backlog - Query Optimization |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
Extend the analyze command to create a "system.<collName>.statistics" collection if it doesn't already exist. The analyze command should also create an index on the "system.<collName>.statistics" collection over "key". |
| Comments |
| Comment by David Storch [ 23/Jun/22 ] |
|
Shouldn't it be "system.statistics.<collName>" to match what we did for time-series collections? This seems like it also models the logical "hierarchy" of namespaces more accurately. |