[SERVER-52524] create secondary indexes on time-series collections Created: 31/Oct/20  Updated: 02/Dec/20  Resolved: 02/Dec/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: Geert Bosch
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Sprint: Execution Team 2020-12-14
Participants:

 Description   

A system.buckets collection should be indexed on `control.max.time`.

We may create one or two secondary indexes depending on whether a metadata field is configured for the time-series collection:

  • Defining a meta field results in two more secondary indexes:
    • { meta: 1, control.max.time: 1 }
    • { control.max.time: 1, meta: 1 }.
  • If no meta field is defined at time series creation time, just one secondary index is created, on { control.max.time: 1 }.


 Comments   
Comment by Geert Bosch [ 02/Dec/20 ]

We're not going to add any secondary indexes by default, as users typically want to index specific metadata fields.

Generated at Thu Feb 08 05:28:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.