[DRIVERS-2161] Add tests for prohibiting explicit readConcern and writeConcern in transaction Created: 18/Jun/19 Updated: 31/Mar/22 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | Transactions |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Major - P3 |
| Reporter: | Oleg Pudeyev (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Needed | ||||||||
| Description |
|
In https://jira.mongodb.org/browse/SPEC-1118 a spec change was made to prohibit passing explicit read concern and write concern to transactions. This spec change is a behavior change for Ruby, and Ruby already implemented transactions by the time the change in 1118 was made, however the 1118 did not spawn a Ruby ticket to implement it. As a result, Ruby is presently not compliant with requirements added in 1118. |
| Comments |
| Comment by Oleg Pudeyev (Inactive) [ 18/Jun/19 ] |
|
Ian asked me to create this ticket because the change in 1118 (which is already in the specifications master) has no corresponding ticket for Ruby, and potentially other drivers, to implement it. Regardless of whether there are spec tests, changes in Ruby are required to be compliant with 1118. If the purpose of this ticket is desired to be to add tests for read/write concerns, this is a little different but fine with me either way. |
| Comment by Jeremy Mikola [ 18/Jun/19 ] |
|
I suggest we rename this to "Add tests for prohibiting explicit readConcern and writeConcern in transaction" since the original spec change was done in SPEC-1118 and this ticket likely only needs to add spec/prose tests. |