[SERVER-73823] Add support for mismatching timeseries spec for $out Created: 09/Feb/23  Updated: 02/Feb/24

Status: In Code Review
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Gil Alon Assignee: Naama Bareket
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-72687 Support for $out to Time-series colle... Closed
depends on SERVER-74061 Support $out for time-series on secon... Closed
Related
related to SERVER-75039 $out should be able to replace a time... Closed
Assigned Teams:
Query Integration
Sprint: Execution Team 2023-02-20, QI 2023-11-13, QI 2023-11-27, QI 2023-12-11, QI 2023-12-25, QI 2024-01-08, QI 2024-01-22, QI 2024-02-05, QI 2024-02-19
Participants:

 Description   

The current implementation of $out for time-series assumes that if $out is replacing an existing time-series collection, the specification the user provides matches the existing time-series collection, and raises an error if not. However, we can try to support changing the specifications of the time-series collection. We need to check if the metaField and timeField are changed, and if so update the indexes of the new collection accordingly. We also need to decide how conflicting options will be handled. 



 Comments   
Comment by Gil Alon [ 27/Sep/23 ]

Reopening this issue because of HELP-50289. Assigning it to myself for now to begin on the syntax changes. The goal of this ticket should just be to change granularity. 

Comment by Gil Alon [ 27/Apr/23 ]

Closing this as won't fix after conversation with Arun. This ticket would change the fundamental behavior of $out. $out always preserves the existing collection options if the target collection exists. This ticket would allow users to change those collection options just for time-series collections. We decided not to add this special behavior just for time-series collections.

Comment by Gil Alon [ 28/Mar/23 ]

Note: we are reverting SERVER-72687 soon, since we want to get SERVER-74061 in with it and we don't think we'll be able to get SERVER-74061 in before 7.0, so this ticket should wait until we merge SERVER-72687 back in.

Generated at Thu Feb 08 06:25:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.