[
https://issues.apache.org/jira/browse/GOBBLIN-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Singh Bora updated GOBBLIN-1440:
--------------------------------------
Description: Currently Add/update/delete of flow specs and cancellation of
a job execution happen via putting/deleting these specs in job catalog.
Listeners of Spec Catalog take appropriate actions. While for add/update/delete
this makes sense to modify job catalog, it makes little sense for job execution
cancellation request to update job catalog in order to trigger the cancellation
because job and execution are two different entities. (was: move cancel job
logic from job catalog listeners to kafkajob monitor and make KafkaJobMonitor's
parseJobSpec() method return the entire JobSpec, so that the caller method
processMessage() can distinguish between a DELETE FLOW and CANCEL JOB requests
and take appropriate actions.)
> move 'cancel trigger code' from job catalog to job monitor
> -----------------------------------------------------------
>
> Key: GOBBLIN-1440
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1440
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: Arjun Singh Bora
> Priority: Major
>
> Currently Add/update/delete of flow specs and cancellation of a job execution
> happen via putting/deleting these specs in job catalog. Listeners of Spec
> Catalog take appropriate actions. While for add/update/delete this makes
> sense to modify job catalog, it makes little sense for job execution
> cancellation request to update job catalog in order to trigger the
> cancellation because job and execution are two different entities.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
