Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
1.5.0
-
None
Description
If no writeConcern is passed to mongoc_collection_create_index_with_opts, it should use the collection's writeConcern, but in fact it uses the default writeConcern.
The NEWS entry for 1.5.0 claiming "mongoc_collection_create_index_with_opts now applies the collection's write concern if none is specified in opts" seems to have been wrong all along.