[SERVER-61780] Investigate if apiVersion should be sent for internal transaction requests Created: 29/Nov/21 Updated: 14/Jan/22 Resolved: 13/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding 2022-01-10, Sharding 2022-01-24 | ||||||||
| Participants: | |||||||||
| Story Points: | 1 | ||||||||
| Comments |
| Comment by Jack Mulrow [ 13/Jan/22 ] |
|
It is legal for a request to not specify any API version parameters (ie apiVersion, apiStrict, and apiDeprecationErrors), and since the uses of the transaction API are all internal, it should be fine to not set any and rely on our testing to surface any problems that come up, which we can then resolve by modifying the caller of the API. |