[SERVER-55240] Support 2d index on time-series collection metadata fields Created: 16/Mar/21 Updated: 05/Aug/21 Resolved: 05/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dan Larkin-York |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | Execution Team 2021-07-12, Execution Team 2021-08-09 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Because metadata does not vary within a bucket, geo indexes on metadata can use an ordinary geo index on the time-series buckets collection. For example,
will become
JS test code
JS test logs
Note: the same query on the corresponding buckets collection works fine, so the index is created via the time-series collection, we just can't use it. |
| Comments |
| Comment by Githook User [ 05/Aug/21 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |
| Comment by Kyle Suarez [ 29/Apr/21 ] |
|
Per louis.williams, we are still doing this work and it will be part of a project to support secondary indexes more generally for time-series metrics. |
| Comment by Kyle Suarez [ 29/Apr/21 ] |
|
dianna.hohensee, is it safe to close this one out? It's still marked as open, so I'm unsure if there were further developments. |
| Comment by Dianna Hohensee (Inactive) [ 22/Mar/21 ] |
|
Closing this out as Won't Do. We do not currently plan to support geo. |