-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Bulk API, Command Logging and Monitoring
-
None
-
Needed - No Spec Changes
-
Summary
DRIVERS-716 introduced command-logging-and-monitoring/tests/monitoring/unacknowledged-client-bulkWrite.yml, which asserts the result of an unacknowledged client-level bulk write (see: 10919c9). This assertion is inconsistent with existing assertions for unacknowledged collection-level bulk writes (e.g. crud/tests/unified/bulkWrite-deleteMany-hint-unacknowledged.yml), despite the client bulk write spec alluding to CRUD: Write Results for modeling unacknowledged results.
At a minimum, the client-level test should be modified to allow for a completely optional BulkWriteResult and assert a possible value of acknowledged=false.
Motivation
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
- is related to
-
DRIVERS-716 Improved Bulk Write API
-
- In Progress
-
- split to
-
CXX-3250 Revise assertion for unacknowledged client bulkWrite result
-
- Backlog
-
-
GODRIVER-3512 Revise assertion for unacknowledged client bulkWrite result
-
- Backlog
-
-
RUBY-3635 Revise assertion for unacknowledged client bulkWrite result
-
- Backlog
-
-
CDRIVER-5934 Revise assertion for unacknowledged client bulkWrite result
-
- In Code Review
-
-
PHPLIB-1645 Revise assertion for unacknowledged client bulkWrite result
-
- In Code Review
-
-
JAVA-5819 Revise assertion for unacknowledged client bulkWrite result
-
- Ready for Work
-
-
RUST-2183 Revise assertion for unacknowledged client bulkWrite result
-
- Ready for Work
-
-
MOTOR-1443 Revise assertion for unacknowledged client bulkWrite result
-
- Closed
-
-
NODE-6868 Revise assertion for unacknowledged client bulkWrite result
-
- Closed
-
-
PYTHON-5222 Revise assertion for unacknowledged client bulkWrite result
-
- Closed
-
-
CSHARP-5530 Revise assertion for unacknowledged client bulkWrite result
-
- Investigating
-