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

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

                Author: ASF GitHub Bot
            Created on: 14/Dec/23 02:26
            Start Date: 14/Dec/23 02:26
    Worklog Time Spent: 10m 
      Work Description: Will-Lo commented on code in PR #3846:
URL: https://github.com/apache/gobblin/pull/3846#discussion_r1426096385


##########
gobblin-service/src/main/java/org/apache/gobblin/service/modules/orchestration/Orchestrator.java:
##########
@@ -299,7 +304,7 @@ public void orchestrate(Spec spec, Properties jobProps, 
long triggerTimestampMil
 
         // Depending on if DagManager is present, handle execution
         if (this.dagManager.isPresent()) {
-          submitFlowToDagManager((FlowSpec) spec, jobExecutionPlanDag);
+          submitFlowToDagManager(flowSpec, jobExecutionPlanDag);

Review Comment:
   Yeah I think we shouldn't need to support a scenario where dagmanager is 
optional given how important it is for lifecycle management





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

    Worklog Id:     (was: 895577)
    Time Spent: 1h 50m  (was: 1h 40m)

> Ensure Adhoc Flows can be Executed in Multi-active Scheduler state
> ------------------------------------------------------------------
>
>                 Key: GOBBLIN-1974
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1974
>             Project: Apache Gobblin
>          Issue Type: Bug
>          Components: gobblin-service
>            Reporter: Urmi Mustafi
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Adhoc flow executions delete the flow spec from the FlowCatalog after adding 
> the spec to the scheduler for the single active scheduler. This makes sense 
> in prior context since the single active scheduler has the information and 
> the spec is no longer needed. However, in the multi-active case we run into a 
> {{No spec found}} error here 
> [https://github.com/apache/gobblin/blob/00c60ca6492644652c66905eb384ab145e348bbf/gobblin-service/src/main/java/org/apache/gobblin/service/monitoring/DagActionStoreChangeMonitor.java#L263].
>  This PR updates the code to delete the spec after persisting it in the adhoc 
> execution case. 



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

Reply via email to