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

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

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


##########
gobblin-service/src/test/java/org/apache/gobblin/service/modules/orchestration/OrchestratorTest.java:
##########
@@ -244,9 +250,10 @@ public void createTopologySpec() {
     }
     // Make sure TopologyCatalog is empty
     Assert.assertTrue(specs.size() == 0, "Spec store should be empty before 
addition");
-    // Make sure TopologyCatalog Listener is empty
-    Assert.assertTrue(specCompiler.getTopologySpecMap().size() == 0, 
"SpecCompiler should not know about any Topology "
-        + "before addition");
+    Assert.assertTrue(specCompiler.getTopologySpecMap().size() == 1, 
"SpecCompiler should know about any Topology "

Review Comment:
   "know about *any*" suggested it would apply even if there were > 1 topo 
specs.  couldn't there be more than one?
   
   also, if non-empty `Set<TopologySpec>` is critical, I was suggesting a guava 
`Precondition` in the ctor





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

    Worklog Id:     (was: 917169)
    Time Spent: 2h 40m  (was: 2.5h)

> initialize topology specs directly from the configs
> ---------------------------------------------------
>
>                 Key: GOBBLIN-2056
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2056
>             Project: Apache Gobblin
>          Issue Type: Improvement
>            Reporter: Arjun Singh Bora
>            Priority: Major
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> initialize topology specs directly from the configs instead of waiting for 
> the callbacks of topology spec catalog listerners



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

Reply via email to