...
...
Background
Some submission are runnable. When a user submits a runnable submission to a queue, the queue's Submission Application would check and start the runnable process. This process could take a long time. We want to provide users the ability to stop their running process at anytime that it is running.
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Current Work Flow
When a user A submits a submission B to queue C, an Submission (immutable object) and SubmissionStatus (mutable object) are created.
Queue C's Application starts the running process for submission B and update submission B's Submission Status.
Proposal
Add the following fields to Submission Status:
| Submission Status |
|---|
| currentFields |
| canCancel : Boolean (Default FALSE) |
| cancelRequested : Boolean (Default FALSE) |
Add an API that allows user to request to cancel their submissions:
Service Layer
Add a new boolean field to submission status called 'cancelRequested'.
...
Add a leaderboard widget, including an executionStatus column. The query should use 'where userId==@CURRENT_USER' to show just the submitter's jobs.
Choose the 'stop button' renderer for this column.
...