The v2 driver’s new Client.BulkWrite API is incompatible with various undocumented parameters like collectionUUID.
Historically C2C has gotten around this by just sending raw commands (e.g., insert) to the server; however, bulkWrite’s response is much more complex to parse than other commands. We would incur a significant maintenance overhead if we wrote our own logic to parse bulkWrite responses.
It would be very useful for us if the driver either:
a) exposed its functionality for parsing bulkWrite responses, or
b) added controls to allow undocumented parameters like bypassEmptyTsReplacement in Client.BulkWrite and other driver APIs.
- is related to
-
GODRIVER-3668 No `bypassEmptyTsReplacement` interface exposed in v2 driver
-
- Closed
-
- related to
-
GODRIVER-3665 Support bypassEmptyTsReplacement in V2 CRUD APIs
-
- Closed
-