[COMPASS-6354] Investigate changes in PM-2945: Unique Constraints for Time-Series Collections Created: 06/Dec/22  Updated: 10/Jan/24  Resolved: 14/Dec/22

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Epic Link: COMPASS-7048
Documentation Changes: Not Needed

 Description   
Original Downstream Change Summary

We forsee downstream impacts across Cloud, Drivers, Devtools, and Docs. This will be flushed out as the design is written.

Description of Linked Ticket

Epic Summary

Summary

Add support for defining a unique index on a time-series collection over the meta and time fields

Motivation

Users frequently ask for unique indexes on time-series collections. Most of the time, they specifically want a unique index on the combination of meta and time. While we cannot efficiently provide unique indexing for arbitrary key specifications, we can handle this combination with some restrictions. Adding this functionality will bring our time-series offering closer to feature parity with our regular collections

Documentation

Product Description
Scope Document
Technical Design Document



 Comments   
Comment by PM Bot [ 10/Jan/24 ]

Fix Version updated for upstream PM-2945:

Generated at Wed Feb 07 22:42:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.