[DRIVERS-2250] SDAM unit test sharded/too_new needs to defined wireVersions for host b Created: 29/Mar/22  Updated: 19/Sep/23

Status: Scheduled
Project: Drivers
Component/s: SDAM
Fix Version/s: None

Type: Spec Change Priority: Minor - P4
Reporter: Neal Beeken Assignee: Warren James
Resolution: Unresolved Votes: 0
Labels: neweng, quick-fix
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to CDRIVER-4727 SDAM unit test sharded/too_new needs ... Blocked
split to CSHARP-4798 SDAM unit test sharded/too_new needs ... Blocked
split to CXX-2757 SDAM unit test sharded/too_new needs ... Blocked
split to GODRIVER-2993 SDAM unit test sharded/too_new needs ... Blocked
split to JAVA-5168 SDAM unit test sharded/too_new needs ... Blocked
split to NODE-5645 SDAM unit test sharded/too_new needs ... Blocked
split to PHPLIB-1242 SDAM unit test sharded/too_new needs ... Blocked
split to PYTHON-3967 SDAM unit test sharded/too_new needs ... Blocked
split to RUBY-3330 SDAM unit test sharded/too_new needs ... Blocked
split to RUST-1766 SDAM unit test sharded/too_new needs ... Blocked
split to MOTOR-1191 SDAM unit test sharded/too_new needs ... Closed
Driver Changes: Needed
Engineering Lead: Shane Harvey Shane Harvey
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4727 Blocked
CXX-2757 Blocked
CSHARP-4798 Blocked
GODRIVER-2993 Blocked
JAVA-5168 Blocked
NODE-5645 Blocked
MOTOR-1191 Duplicate
PYTHON-3967 Blocked
PHPLIB-1242 Blocked
RUBY-3330 Blocked
RUST-1766 Blocked

 Description   

Summary

What is the problem or use case, what are we trying to achieve?

SDAM unit test sharded/too_new needs to defined wireVersions for host b. Host b omits a wire version which causes an incompatibility error for having too low a wireVersion since drivers now require the wire version to be greater than 6. The test intends to test for host a's wireVersion set to 999, but if a driver does not correctly check for "too new" wire versions their topology will still be marked incompatible by host b's omission.

Test file here

Motivation

Who is the affected end user?

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?

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?

Does this ticket have any functional impact, or is it just test improvements?


Generated at Thu Feb 08 08:25:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.