[DRIVERS-2270] Use $$unsetOrMatches for upsert and multi in update command expectations Created: 07/Apr/22 Updated: 20/May/22 |
|
| Status: | Implementing |
| Project: | Drivers |
| Component/s: | CRUD |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Unknown |
| Reporter: | Jeremy Mikola | Assignee: | Jeremy Mikola |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | yaml-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Downstream Changes Summary: | Sync unified CRUD spec tests with mongodb/specifications@51ca03b. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
SummaryThe update command expectations in various let and comment option tests from DRIVERS-1788 and Ultimately, we can consider requiring drivers to leave these fields unset by default (DRIVERS-2271), but for now spec tests will need to use $$unsetOrMatches for portability. MotivationWho is the affected end user?Drivers that explicitly specify false for upsert and/or multi options in update statements. How does this affect the end user?APM assertions fail. Is this issue urgent?This is only urgent for drivers that explicitly send false for upsert and multi options. Is this ticket required by a downstream team?No. Is this ticket only for tests?Yes. |
| Comments |
| Comment by Githook User [ 11/Apr/22 ] |
|
Author: {'name': 'Jeremy Mikola', 'email': 'jmikola@gmail.com', 'username': 'jmikola'}Message: DRIVERS-2270: Use $$unsetOrMatches for upsert and multi (#1174) |
| Comment by Jeremy Mikola [ 08/Apr/22 ] |