[SERVER-65840] Allow returning any type from the callback given to the transaction API Created: 20/Apr/22 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-nyc-subteam2, txn-api-improvements | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||
| Participants: | |||||||||
| Story Points: | 5 | ||||||||
| Description |
|
Currently, the callback given to the transaction API must return void so callers have to use shared state to return values from the callback to the API caller. Instead the API should allow the callback to return any type and the response from the various transaction run() methods should return that type, in addition to the currently returned CommitResult. |
| Comments |
| Comment by Jason Zhang [ 11/Jan/23 ] |
|
Moving this ticket out of PM-1632 since it's not a must-do for that project. |
| Comment by Jack Mulrow [ 28/Apr/22 ] |
|
This is a nice cleanup, but may be tricky, so moving to PM-1632 because that is the next project that will use the transaction API and we'll have more time to get to this then. |