-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 8.2.0-rc0
-
Component/s: Write Ops
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
CAR Team 2025-07-21
-
200
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
raw_operation_utils.js has an isBinaryCompatibleFlagEnabledAndStable utility, which should return true if all binaries in the cluster have a binary-compatible feature flag enabled, and false otherwise.
However the current implementation of function has two issues for multiversion suites:
- It assumes the version of the feature flag document returned by getParameter contains the minimum version at which the flag is enabled. However binary-compatible feature flags do not have a version: X.Y declaration in .idl, and instead the version is always the latest binVersion.
- The function currently only returns true once the flag is enabled on both lastLTS and lastContinuous. Once v8.3 is released, tests like timeseries_raw_data_getmore.js, will start running on mixed lastContinuous+latest suites, yet the utility will incorrectly return that the flag can not be used.
Fix the handling of multiversion suites in the utility.
- causes
-
SERVER-107756 Fix isRawOperationSupported when called inside a transaction
-
- Closed
-
- is depended on by
-
SERVER-107079 Upgrade FCV Constants and Tag the first new commit in master with 8.3.0-alpha0
-
- Closed
-