-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Server Selection
-
None
-
Needed
Summary
Add a server selection test to ensure the empty tag set {} matches servers with no tags.
Motivation
Motivated by a bug in the Rust driver: RUST-2363
Who is the affected end user?
Users using read preferences with tag sets.
How does this affect the end user?
If this surfaces a bug, this could cause an incorrect server to be selected.
How likely is it that this problem or use case will occur?
Unsure. C and PyMongo do not appear to have this bug. But I think it is worth syncing the new spec test to check all drivers.
If the problem does occur, what are the consequences and how severe are they?
Unsure. This might distribute load in a different way than the user intended.
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
Acceptance Criteria
- Ensure a new test fails on the Rust driver prior to the fix of RUST-2363.
- is related to
-
RUST-2363 Empty tag set rejects servers with no tags
-
- In Code Review
-
- split to
-
CDRIVER-6244 Test empty tag sets match servers with no tag sets
-
- Blocked
-
-
CSHARP-5891 Test empty tag sets match servers with no tag sets
-
- Blocked
-
-
CXX-3420 Test empty tag sets match servers with no tag sets
-
- Blocked
-
-
GODRIVER-3821 Test empty tag sets match servers with no tag sets
-
- Blocked
-
-
JAVA-6104 Test empty tag sets match servers with no tag sets
-
- Blocked
-
-
NODE-7451 Test empty tag sets match servers with no tag sets
-
- Blocked
-
-
PHPLIB-1792 Test empty tag sets match servers with no tag sets
-
- Blocked
-
-
PYTHON-5730 Test empty tag sets match servers with no tag sets
-
- Blocked
-
-
RUBY-3777 Test empty tag sets match servers with no tag sets
-
- Blocked
-
-
RUST-2364 Test empty tag sets match servers with no tag sets
-
- Blocked
-