The "delete" operation for job executions is implemented in the saharaclient and is used by the UI and the CLI. This calls the v1.1 REST API function "/job-executions/<job_execution_id>".
Currently, this method delete the job execution object in the Sahara database but it does not stop a running job (in Oozie, for example). There is a "cancel" method in the REST API but the client does not implement an interface to it.
So, we need some way to cancel a job, I believe. Do we want the current "delete" to cancel-and-delete , or do we want to implement cancel in the client and be able to call both?
Consider relaunch, it is a useful feature. Imagine:
1) Launch a job, realize the args are wrong
2) Cancel
3) Relaunch
If delete stops the job and also wipes out the job execution record, the relaunch behavior becomes much harder in the UI. The UI must remember the details.
Note, current CR for V2 API doesn't list cancel as an option.
https://review.openstack.org/#/c/70627/6
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit e4eb90d38adf70c
Author: Andrey Pavlov <email address hidden>
Date: Thu Oct 16 12:27:14 2014 +0400
Added cancel before deleting job execution
Now delete method will stop running job before
deleting job execution object in database
Change-Id: Id61f0348b8043a
Closes-bug: #1329431