[
https://issues.apache.org/jira/browse/GOBBLIN-2134?focusedWorklogId=934345&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-934345
]
ASF GitHub Bot logged work on GOBBLIN-2134:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 11/Sep/24 19:59
Start Date: 11/Sep/24 19:59
Worklog Time Spent: 10m
Work Description: arjun4084346 commented on code in PR #4049:
URL: https://github.com/apache/gobblin/pull/4049#discussion_r1755505617
##########
gobblin-restli/gobblin-flow-config-service/gobblin-flow-config-service-api/src/main/pegasus/org/apache/gobblin/service/ExecutionStatus.pdl:
##########
@@ -49,4 +49,9 @@ enum ExecutionStatus {
* Flow cancelled.
*/
CANCELLED
+
+ /**
+ * Flow or job is skipped
Review Comment:
i think it just comes down to how we define things. imo, when a flow
execution is skipped when there is already an execution for the same flow is
running, status SKIPPED sounds more appropriate.
Issue Time Tracking
-------------------
Worklog Id: (was: 934345)
Time Spent: 1h 20m (was: 1h 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: 1h 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
