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

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

                Author: ASF GitHub Bot
            Created on: 01/Mar/24 19:56
            Start Date: 01/Mar/24 19:56
    Worklog Time Spent: 10m 
      Work Description: phet commented on code in PR #3886:
URL: https://github.com/apache/gobblin/pull/3886#discussion_r1509469273


##########
gobblin-temporal/src/main/java/org/apache/gobblin/temporal/ddm/workflow/impl/NestingExecOfProcessWorkUnitWorkflowImpl.java:
##########
@@ -41,7 +41,7 @@ public class NestingExecOfProcessWorkUnitWorkflowImpl extends 
AbstractNestingExe
       .build();
 
   private static final ActivityOptions ACTIVITY_OPTS = 
ActivityOptions.newBuilder()
-      .setStartToCloseTimeout(Duration.ofSeconds(999))
+      .setStartToCloseTimeout(Duration.ofMinutes(20))

Review Comment:
   I definitely agree on configurability.  I added a TODO [over 
there](https://github.com/apache/gobblin/pull/3886/files#diff-8b215b0860cefa8c3d067f90482ea09e09bfab64ede78e369c863240e0c28dfaR55)
 and can add one here too





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

    Worklog Id:     (was: 907853)
    Time Spent: 50m  (was: 40m)

> Implement Gobblin-on-Temporal End-to-End Workflow
> -------------------------------------------------
>
>                 Key: GOBBLIN-2010
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2010
>             Project: Apache Gobblin
>          Issue Type: New Feature
>          Components: gobblin-core
>            Reporter: Kip Kohn
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Provide a complete capability to execute a full Gobblin job through 
> Temporal.io. This follows on 
> https://issues.apache.org/jira/browse/GOBBLIN-1945 and 
> https://issues.apache.org/jira/browse/GOBBLIN-2007 .  Thereafter it will be 
> possible to provide an arbitrary `JobState` config that specifies the 
> intended `Source`, `Writer`, Publisher`, `Converter` etc. in order to carry 
> out whatever Data Movement is desired.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to