-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Component/s: SDAM
-
None
-
Not Needed
Summary
The SDAM spec tests in the mongo server repository here:
https://github.com/mongodb/mongo/tree/master/src/mongo/client/sdam/json_tests/sdam_tests
Are out of sync with the drivers SDAM spec tests. The drivers version has changed to using hello over legacy hello, and server has made changes to some properties on test cases.
Motivation
Who is the affected end user?
All drivers running SDAM tests
Who are the stakeholders?
How does this affect the end user?
Are they blocked? Are they annoyed? Are they confused?
How likely is it that this problem or use case will occur?
Main path? Edge case?
If the problem does occur, what are the consequences and how severe are they?
Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?
Is this issue urgent?
Yes
Does this ticket have a required timeline? What is it?
Is this ticket required by a downstream team?
Needed by e.g. Atlas, Shell, Compass?
Is this ticket only for tests?
Is this ticket have any functional impact, or is it just test improvements?
It's tests that potentially reveal failures for driver's SDAM implementations
- is depended on by
-
DRIVERS-1954 SDAM should give priority to electionId over setVersion when updating topology
- Closed
- related to
-
SERVER-63399 Update driver SDAM tests
- Backlog