[DRIVERS-2145] Add tests for passing write concern to $out and $merge pipelines Created: 10/Jun/19  Updated: 31/Mar/22

Status: Backlog
Project: Drivers
Component/s: CRUD
Fix Version/s: None

Type: Spec Change Priority: Major - P3
Reporter: Jeremy Mikola Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Driver Changes: Needed

 Description   

Per jeff.yemin's comment in mongodb/specifications#563:

Can we add tests that assert both $out and $merge are treated as writes, e.g. by specifying a non-default write concern and including the write concern in the command started event?

The CRUD spec currently has no syntax for specifying database or collection-level options. While clientOptions were introduced in 5cf02a5 (SPEC-1210), they are not currently used in any tests and might not be supported a driver's spec test runner.

I propose we introduce the database and collection-level options, as exist in the transactions spec test format, and add these tests.


Generated at Thu Feb 08 08:24:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.