[SERVER-56238] Queries on time field do not use index on time field on non-clustered time-series collections Created: 21/Apr/21 Updated: 27/Oct/23 Resolved: 14/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Gregory Noma | Assignee: | Backlog - Query Optimization |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently, it is possible for a time-series collection to not be clustered by _id, either by the (undocumented) timeseriesBucketsCollectionClusterById server parameter or if using a storage engine that doesn't support clustered indexes, like ephemeralForTest. When this is the case, any queries on the time field appear to use the _id index, even if there is also an index on the time field. See this test. |
| Comments |
| Comment by Louis Williams [ 14/Jun/21 ] |
|
Closing because I'm implementing support for clustered indexes in EFT in |