[DRIVERS-1646] Investigate changes in PM-2189: Secondary Indexes on time-series metrics Created: 05/Apr/21 Updated: 27/May/22 Resolved: 19/Apr/21 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Driver Changes: | Needed | ||||
| Server Compat: | 5.2, 5.3 | ||||
| Upstream Changes Summary: |
|
||||
| Description |
|
Downstream Change Summary We expect downstream impact will be needed for all teams. To be determined during scoping. Description of Linked TicketEpic Summary SummaryTime-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. MotivationQuery 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 |
| Comments |
| Comment by Esha Bhargava [ 19/Apr/21 ] |
|
No driver changes needed. |