Queries on time field do not use index on time field on non-clustered time-series collections

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Query Optimization
              Reporter:
              Gregory Noma
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: