-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
ALL
-
v7.3
-
There was investigation work done for this in SERVER-86319 but we didn't think about the downgrade implications of version 3 buckets.
One option is to backport a change so that the query system treats version 3 buckets the same as version 2, as the sorted by time-field property is not used in earlier server versions. I believe we'll need to release version 7.0 with this change before 8.0 is released so that users can downgrade if needed. But we should also do something for 5.0 and 6.0.
uncaught exception: Error: error: { "ok" : 0, "errmsg" : "PlanExecutor error during aggregation :: caused by :: Invalid bucket version", "code" : 5857900, "codeName" : "Location5857900", "$clusterTime" : { "clusterTime" : Timestamp(1716427644, 9), "signature" : { "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="), "keyId" : NumberLong(0)
- is related to
-
SERVER-91303 Block downgrading from 8.0->7.X if time-series collections are present
- Closed
- related to
-
SERVER-86319 Investigate query code checking time-series bucket versions
- Closed