-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Sessions, Transactions
Use Case
As an... Atlas user
I want... Atlas commands to not fail if I'm using a session with a read/write concern specified
So that... I can reuse my sessions for non-Atlas specific and Atlas specific operations.
Unknowns
- How do we not add readConcern / writeConcern to a listSearchIndexes command since its commandName is 'aggregate'?
Acceptance Criteria
Implementation Requirements
- update applySession so that in the following cases a read/write concern is not appended to the command object
- session.supports.CausalConsistency
- snapshot = true
Testing Requirements
- unskip tests with TODO(NODE-6047)
Documentation Requirements
- DOCSP ticket, API docs, etc
- has to be done after
-
NODE-5745 Avoid Appending Write/Read Concern in Atlas Search Index Helper Commands
-
- Closed
-