-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Fully Compatible
-
v8.0, v7.0
-
Execution Team 2024-04-01, Execution Team 2024-04-29, Execution Team 2024-07-08, Execution Team 2024-07-22, Execution Team 2024-08-19, Execution Team 2024-10-14, Execution Team 2024-10-28, Execution Team 2024-11-11, Execution Team 2024-11-25
-
200
SERVER-86451 introduced a change in behavior where inconsistencies detected with time-series collections during validation would error instead of creating a warning. As a result of this, some tests that would previously pass with warnings were now failing. One of the changes in this ticket involved disabling this check and this check in testing. This ticket would look into the behavior causing the inconsistencies and re-enable the checks. Also, as part of this, some integration tests had validation disabled on shutdown - this ticket could look into re-enabling this test as well.
For the check comparing the control.min timestamp and the observed min timestamp, after some discussion it appears that checking for strict equality is not enforceable when granularity is modified. Tentatively a bound on this would be control.min >= observed min timestamp - rounding seconds - this still caused the test to fail, so this ticket would build off of that.
- depends on
-
SERVER-95480 Validate will fail the min/max check for time-series collections that have had their granularity changed
-
- Closed
-
- is cloned by
-
-
- Closed
-
- is depended on by
-
SERVER-88043 Make time-series validation failures errors in production
-
- Open
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
-
- Closed
-