[GODRIVER-2649] Fix ReadConcern logic on RunCommand Created: 09/Nov/22 Updated: 06/Dec/23 Resolved: 06/Nov/23 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.0, 1.13.0, 1.13.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Benji Rewis (Inactive) | Assignee: | Preston Vasquez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Go Driver 2.0: Driver |
| Backwards Compatibility: | Major Change |
| Documentation Changes: | Not Needed |
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
| Description |
|
readConcern is not currently passed to the underlying operation in command.go. This means that ReadConcern is effectively a no-op, and when we try to pass the Database read concern, here, it is not actually inherited by the operation. We should pass readConcern to the underlying operation, but this would be backward-breaking, so we should wait until the next major release of the driver to fix this small bug. Open questions:
|
| Comments |
| Comment by Githook User [ 03/Nov/23 ] |
|
Author: {'name': 'Steven Silvester', 'email': 'steven.silvester@ieee.org', 'username': 'blink1073'}Message: Co-authored-by: Preston Vasquez <prestonvasquez@icloud.com> |
| Comment by Githook User [ 09/Nov/22 ] |
|
Author: {'name': 'Benjamin Rewis', 'email': '32186188+benjirewis@users.noreply.github.com', 'username': 'benjirewis'}Message: Co-authored-by: Matt Dale <9760375+matthewdale@users.noreply.github.com> |