-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Service Arch
-
Fully Compatible
-
Service Arch 2024-02-05
-
158
-
4
The ValidatedTenancyScope is not available on the opCtx in the Distinct command specifically for transactions. It's possible this is due to transactions operating on a separate thread, but this may need additional investigating. Unfortunately, the distinct command is derived from BasicCommand, which means we cannot access the original OpMsgRequest for the VTS, which is needed to build the DistinctCommandRequest IDL structured request.
This is first discovered failing one of two identical distinct commands in the view_reads_in_transactions.js test, one within a transaction and one outside of a transaction. This applies to the native_tenant_data_isolation_with_security_token_jscore_passthrough as the VTS reflects the state of the security token.
- depends on
-
SERVER-81787 Add support for ValidatedTenancyScope to ForwardableOperationMetadata
- Closed
- is depended on by
-
SERVER-85479 Make UMCTransaction to build OpMsgRequest with ValidatedTenancyScope
- Closed