[SERVER-35007] Ensure that transactions fail when run with OP_QUERY Created: 15/May/18 Updated: 27/Oct/23 Resolved: 15/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Sprint: | Repl 2018-06-04 | ||||||||
| Participants: | |||||||||
| Comments |
| Comment by Spencer Brody (Inactive) [ 15/May/18 ] |
|
We must support running a find command via OP_QUERY (by doing a query on db.$cmd), and using OP_QUERY directly has no way to even express the transaction-related arguments, so there's no server work to do here. |