[
https://issues.apache.org/jira/browse/GOBBLIN-2056?focusedWorklogId=917143&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-917143
]
ASF GitHub Bot logged work on GOBBLIN-2056:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/May/24 16:19
Start Date: 01/May/24 16:19
Worklog Time Spent: 10m
Work Description: umustafi commented on code in PR #3937:
URL: https://github.com/apache/gobblin/pull/3937#discussion_r1586473269
##########
gobblin-service/src/main/java/org/apache/gobblin/service/modules/utils/FlowCompilationValidationHelper.java:
##########
@@ -73,12 +74,12 @@ public class FlowCompilationValidationHelper {
@Inject
public FlowCompilationValidationHelper(Config config,
SharedFlowMetricsSingleton sharedFlowMetricsSingleton,
- UserQuotaManager userQuotaManager, FlowStatusGenerator
flowStatusGenerator) {
Review Comment:
Yes I see that but what is the `waiting` you refer to in description "making
spec compiler as a topology spec catalog listener and then wait for topology
spec catalog to populate topologies." How do you know the `topologySpecCatalog`
is populated?
Issue Time Tracking
-------------------
Worklog Id: (was: 917143)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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)
