[
https://issues.apache.org/jira/browse/GOBBLIN-2134?focusedWorklogId=931235&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-931235
]
ASF GitHub Bot logged work on GOBBLIN-2134:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Aug/24 20:52
Start Date: 21/Aug/24 20:52
Worklog Time Spent: 10m
Work Description: arjun4084346 commented on PR #4029:
URL: https://github.com/apache/gobblin/pull/4029#issuecomment-2302992856
> Need to test this thoroughly with unit tests, I believe this can cause the
JobStatusMonitor to have some issues since it doesn't have SKIPPED in the
JobStatusMonitor ordered execution statuses?
This change is not emitting SKIPPED event, so JobStatusMonitor will never
get any such event. It is just updating the status in DagNode. But yes, let me
update the code to actually emit the event so `get job status` call show the
job status as SKIPPED; and incorporate it in ORDERED_EXECUTION_STATUS
Issue Time Tracking
-------------------
Worklog Id: (was: 931235)
Time Spent: 20m (was: 10m)
> update job status to SKIPPED for all the dependent jobs of a cancelled job
> --------------------------------------------------------------------------
>
> Key: GOBBLIN-2134
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2134
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: Arjun Singh Bora
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
