Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-1646

Investigate changes in PM-2189: Secondary Indexes on time-series metrics

    XMLWordPrintableJSON

Details

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Needed
    • Hide
      • The createIndexes command will support building additional index types on time-series collections:
      • On the metadata field, partial, 2d and 2dsphere index types will be supported.
      • On the measurement field, ascending, descending, 2dsphere and partial index types will be supported.
      • Compound index key patterns that are currently supported on regular collections will be supported on time-series collections.
      • An ascending/descending index on a measurement field can't be multikey.
      • Running listIndexes on a system.buckets.* collection will list the "originalSpec" field for indexes which is used when mapping between the time-series view and underlying bucket collection.
      • When downgrading FCV, any incompatible index types on earlier versions will need to be dropped, otherwise, the FCV downgrade will fail.
      Show
      The createIndexes command will support building additional index types on time-series collections: On the metadata field, partial, 2d and 2dsphere index types will be supported. On the measurement field, ascending, descending, 2dsphere and partial index types will be supported. Compound index key patterns that are currently supported on regular collections will be supported on time-series collections. An ascending/descending index on a measurement field can't be multikey. Running listIndexes on a system.buckets.* collection will list the "originalSpec" field for indexes which is used when mapping between the time-series view and underlying bucket collection. When downgrading FCV, any incompatible index types on earlier versions will need to be dropped, otherwise, the FCV downgrade will fail.

    Description

      Downstream Change Summary

      We expect downstream impact will be needed for all teams. To be determined during scoping.

      Description of Linked Ticket

      Epic Summary

      Summary

      Time-series collections currently only support indexing static metadata fields. Implement support for indexing metrics that vary over time. Use cases include tracking moving vehicles, selectively indexing metrics that fall within certain geographical boundaries, and selectively deleting data for old metrics automatically.

      Motivation

      Query patterns and use cases highlight the importance for customers to freely index measurement values to have better performance and accomplish the level of analysis they want to complete. Use cases such as geospatial IoT, e.g. fleet monitoring, and text searching, e.g. devops, will require users to create secondary indexes on the actual measurements being collected in time series collections.

      Cast of Characters

      Documentation

      Scope Document
      Technical Design Document

      Attachments

        Activity

          People

            Unassigned Unassigned
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: