-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
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, QI 2024-03-04, QI 2024-03-18, QI 2024-04-01, QI 2024-04-15, QI 2024-04-29, QI 2024-05-13, QI 2024-05-27, QI 2024-06-10, QI 2024-06-24, QI 2024-07-08, QI 2024-07-22, QI 2024-08-05
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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.
- depends on
-
SERVER-72687 Support for $out to Time-series collections
-
- Closed
-
-
SERVER-74061 Support $out for time-series on secondaries and sharded clusters
-
- Closed
-
- related to
-
-
- Closed
-