-
Type: Improvement
-
Resolution: Done
-
Priority: Unknown
-
None
-
Component/s: Collection Management
-
None
-
Not Needed
-
Summary
New time series collection options were backported to MongoDB 6.3. The tests were introduced in DRIVERS-2546.
Motivation
Who is the affected end user?
Who are the stakeholders?
How does this affect the end user?
Are they blocked? Are they annoyed? Are they confused?
How likely is it that this problem or use case will occur?
Main path? Edge case?
If the problem does occur, what are the consequences and how severe are they?
Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?
Is this issue urgent?
Does this ticket have a required timeline? What is it?
Is this ticket required by a downstream team?
Needed by e.g. Atlas, Shell, Compass?
Is this ticket only for tests?
Does this ticket have any functional impact, or is it just test improvements?
Acceptance Criteria
What specific requirements must be met to consider the design phase complete?
- split to
-
CDRIVER-4720 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed
-
CSHARP-4785 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed
-
CXX-2747 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed
-
GODRIVER-2980 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed
-
JAVA-5147 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed
-
MOTOR-1188 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed
-
NODE-5624 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed
-
PHPLIB-1232 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed
-
PYTHON-3955 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed
-
RUBY-3326 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed
-
RUST-1760 Run timeSeries collection creation options tests on MongoDB 6.3
- Closed