[
https://issues.apache.org/jira/browse/GOBBLIN-2020?focusedWorklogId=910962&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910962
]
ASF GitHub Bot logged work on GOBBLIN-2020:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Mar/24 20:39
Start Date: 21/Mar/24 20:39
Worklog Time Spent: 10m
Work Description: Will-Lo commented on code in PR #3900:
URL: https://github.com/apache/gobblin/pull/3900#discussion_r1534646041
##########
gobblin-temporal/src/main/java/org/apache/gobblin/temporal/ddm/activity/impl/CommitActivityImpl.java:
##########
@@ -135,6 +137,12 @@ public Callable<Void> apply(final Map.Entry<String,
JobState.DatasetState> entry
IteratorExecutor.logFailures(result, null, 10);
+ for (JobState.DatasetState datasetState : datasetStatesByUrns.values()) {
+ // Set the overall job state to FAILED if the job failed to process
any dataset
+ if (datasetState.getState() == JobState.RunningState.FAILED) {
+ throw new IOException("Failed to commit dataset state for dataset "
+ datasetState.getDatasetUrn());
Review Comment:
It should already be logged in `SafeDatasetCommit`, the challenge here is to
group them all into one exception and log that. I'll try it out
Issue Time Tracking
-------------------
Worklog Id: (was: 910962)
Time Spent: 1h (was: 50m)
> Fixes failed workflow paths in Temporal to properly emit GTE and fail job
> when commit fails
> -------------------------------------------------------------------------------------------
>
> Key: GOBBLIN-2020
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2020
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: William Lo
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> There are a few bugs in Gobblin-Temporal execution mode:
> 1. If the publishing step fails, the activity does not report a failure due
> to missing a step post commit to check the dataset states
> 2. No GTEs are emitted upon job failure, which makes tracking difficult
> 3. Some metadata propagation for flow execution ID with workflows is
> incorrect due to a bug reading worker configs instead of job props
> 4. The GenerateWus activity does not return the right number of workunits
> created due to counting top level multiworkunits
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
