Summary
The original spec tests for DRIVERS-823 ($out/$merge on secondaries) included assertions that a client-level readConcern option would be passed to pre-5.0 servers. Read concerns for write stages were not generally supported before MongoDB 4.2 (DRIVERS-610), so those tests should specify a lower version requirement to avoid potential failures.
Motivation
Who is the affected end user?
Driver test suites.
How does this affect the end user?
Failing tests for pre-4.2 server versions.
How likely is it that this problem or use case will occur?
Always, unless a driver is sending readConcern to pre-4.2 servers and no server-side error is raised. The tests happen to use read concern level "local", so it's possible that it would be silently ignored (I've not verified that).
If the problem does occur, what are the consequences and how severe are they?
Minor annoyance with a failing test; however, this should not affect users.
Is this issue urgent?
Drivers may consider this urgent to resolve failing CI.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
- is related to
-
DRIVERS-823 Support $merge and $out executing on secondaries
- In Progress
-
DRIVERS-610 Add support for majority read concern level to Aggregation $out
- Closed
- split to
-
GODRIVER-2195 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Closed
-
PHPLIB-745 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Closed
-
JAVA-4363 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Closed
-
CXX-2396 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Backlog
-
NODE-3694 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Closed
-
CDRIVER-4195 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Closed
-
CSHARP-3925 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Closed
-
MOTOR-839 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Closed
-
PYTHON-2954 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Closed
-
RUBY-2818 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Closed
-
RUST-1067 aggregate-write-readPreference tests should not expect readConcern to be passed to pre-4.2 servers
- Closed