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

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

                Author: ASF GitHub Bot
            Created on: 06/May/24 20:30
            Start Date: 06/May/24 20:30
    Worklog Time Spent: 10m 
      Work Description: phet commented on code in PR #3944:
URL: https://github.com/apache/gobblin/pull/3944#discussion_r1591517872


##########
gobblin-service/src/test/java/org/apache/gobblin/service/modules/orchestration/OrchestratorTest.java:
##########
@@ -127,19 +133,31 @@ public void setup() throws Exception {
 
     SharedFlowMetricsSingleton sharedFlowMetricsSingleton = new 
SharedFlowMetricsSingleton(ConfigUtils.propertiesToConfig(orchestratorProperties));
 
-    this.orchestrator = new 
Orchestrator(ConfigUtils.propertiesToConfig(orchestratorProperties),
-        this.topologyCatalog, mockDagManager, Optional.of(logger), 
mockStatusGenerator,
-        Optional.of(mockFlowTriggerHandler), sharedFlowMetricsSingleton, 
Optional.of(mock(FlowCatalog.class)), Optional.of(dagManagementStateStore),
-        new FlowCompilationValidationHelper(config, 
sharedFlowMetricsSingleton, mock(UserQuotaManager.class), mockStatusGenerator));
-    this.topologyCatalog.addListener(orchestrator);
-    this.flowCatalog.addListener(orchestrator);
+    FlowCompilationValidationHelper flowCompilationValidationHelper = new 
FlowCompilationValidationHelper(config, sharedFlowMetricsSingleton, 
mock(UserQuotaManager.class), mockFlowStatusGenerator);
+    this.dagMgrNotFlowLaunchHandlerBasedOrchestrator = new 
Orchestrator(ConfigUtils.propertiesToConfig(orchestratorProperties),

Review Comment:
   renamed to avoid confusion, as I now pass `Optional.absent()` for the 
`FlowLaunchHandler`.  nothing about the previously-existing tests below 
strictly validated that code path, so I made this entire `OrchestratorTest` 
class specific to the legacy `DagManager` version of `Orchestrator`.
   
   as for the lack of validation for the other code path, that suggests a 
missing test: e.g. that `orchestrate` invokes 
`FlowLaunchHandler::handleFlowLaunchTriggerEvent`
   
   cc: @umustafi and @arjun4084346 





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

    Worklog Id:     (was: 917934)
    Time Spent: 1h 10m  (was: 1h)

> adhoc flow failure due to concurrent execs must be removed from flow catalog
> ----------------------------------------------------------------------------
>
>                 Key: GOBBLIN-2062
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2062
>             Project: Apache Gobblin
>          Issue Type: New Feature
>          Components: gobblin-service
>            Reporter: Kip Kohn
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> the Orchestrator + DagManager MUST remove adhoc flows that violate concurrent 
> execs from the flow catalog.  otherwise gaas will continue to return '409 
> Conflict' to each subsequent attempt to create an adhoc flow with the same 
> flowGroup+flowName.  this is despite the fact that the flow (which still 
> remains in the FlowCatalog, when it shouldn't be) already has the status 
> FAILED, which is a "final status".



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

Reply via email to