-
Type:
Spec Change
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Component/s: Bulk API
-
None
-
Needed
Summary
The paragraph following the BulkWrite example used lowercase "must" (non-RFC 2119) and did not repeat the "MUST NOT send any operations" condition, leaving the rejection timing ambiguous (pre-flight vs. on first encountered error). Rewrite with RFC 2119 MUST and make the pre-flight nature explicit.
Motivation
Who is the affected end user?
Driver authors implementing BulkWrite with collation validation on pre-3.4 servers.
Is this issue urgent?
No.
Is this ticket only for tests?
No — spec text clarification.
Acceptance Criteria
PR merged: https://github.com/mongodb/specifications/pull/1941
- related to
-
DRIVERS-3491 Spec analysis: collation — missing tests, ambiguities, inconsistencies
-
- Backlog
-
- split to
-
CDRIVER-6336 Clarify BulkWrite pre-flight check timing in collation spec
-
- Blocked
-
-
CSHARP-6049 Clarify BulkWrite pre-flight check timing in collation spec
-
- Blocked
-
-
CXX-3498 Clarify BulkWrite pre-flight check timing in collation spec
-
- Blocked
-
-
GODRIVER-3914 Clarify BulkWrite pre-flight check timing in collation spec
-
- Blocked
-
-
JAVA-6208 Clarify BulkWrite pre-flight check timing in collation spec
-
- Blocked
-
-
NODE-7588 Clarify BulkWrite pre-flight check timing in collation spec
-
- Blocked
-
-
PHPLIB-1856 Clarify BulkWrite pre-flight check timing in collation spec
-
- Blocked
-
-
PYTHON-5831 Clarify BulkWrite pre-flight check timing in collation spec
-
- Blocked
-
-
RUBY-3883 Clarify BulkWrite pre-flight check timing in collation spec
-
- Blocked
-
-
RUST-2431 Clarify BulkWrite pre-flight check timing in collation spec
-
- Blocked
-