[ 
https://issues.apache.org/jira/browse/GOBBLIN-2020?focusedWorklogId=910953&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910953
 ]

ASF GitHub Bot logged work on GOBBLIN-2020:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 21/Mar/24 19:30
            Start Date: 21/Mar/24 19:30
    Worklog Time Spent: 10m 
      Work Description: homatthew commented on code in PR #3900:
URL: https://github.com/apache/gobblin/pull/3900#discussion_r1534546898


##########
gobblin-temporal/src/main/java/org/apache/gobblin/temporal/ddm/activity/impl/CommitActivityImpl.java:
##########
@@ -64,9 +64,11 @@ public class CommitActivityImpl implements CommitActivity {
   public int commit(WUProcessingSpec workSpec) {
     // TODO: Make this configurable
     int numDeserializationThreads = DEFAULT_NUM_DESERIALIZATION_THREADS;
+    String jobName = "";

Review Comment:
   Non empty string would be helpful so that it's obvious that we never got to 
line 71





Issue Time Tracking
-------------------

    Worklog Id:     (was: 910953)
    Time Spent: 20m  (was: 10m)

> 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: 20m
>  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)

Reply via email to