[CXX-1387] Bulk write operations don't inherit write concern from the collection Created: 07/Jul/17 Updated: 28/Oct/23 Resolved: 28/Jul/17 |
|
| Status: | Closed |
| Project: | C++ Driver |
| Component/s: | Implementation |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samuel Rossi (Inactive) | Assignee: | Samuel Rossi (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Case: | (copied to CRM) |
| Description |
|
In our implementation of collection::bulk_write, we're currently not using the collection's write concern due to the call to libmongoc::bulk_operation_set_collection getting a new mongoc_collection_t from the client rather than using the existing one with the options set. To remedy this, we should replace the call to libmongoc::bulk_operation_new in the constructor for bulk_write with a call to libmongoc::collection_create_bulk_operation, which properly handles inheriting the write concern from the collection. |
| Comments |
| Comment by Githook User [ 28/Jul/17 ] |
|
Author: {'email': 'saghmrossi@gmail.com', 'username': 'saghm', 'name': 'Saghm Rossi'}Message: |