[
https://issues.apache.org/jira/browse/GOBBLIN-1705?focusedWorklogId=809712&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-809712
]
ASF GitHub Bot logged work on GOBBLIN-1705:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 17/Sep/22 01:44
Start Date: 17/Sep/22 01:44
Worklog Time Spent: 10m
Work Description: arjun4084346 commented on code in PR #3557:
URL: https://github.com/apache/gobblin/pull/3557#discussion_r973524101
##########
gobblin-runtime/src/main/java/org/apache/gobblin/runtime/spec_catalog/FlowCatalog.java:
##########
@@ -457,4 +458,15 @@ public void remove(URI uri, Properties headers, boolean
triggerListener) {
public Object getSyncObject(String specUri) {
return this.specSyncObjects.getOrDefault(specUri, null);
}
+
+ public Spec getSpecFromStore(String specUri) {
Review Comment:
We should have the same name of the method, i.e. getSpecs(String uri) throws
SpecNotFoundException
Issue Time Tracking
-------------------
Worklog Id: (was: 809712)
Time Spent: 1h 50m (was: 1h 40m)
> New Consumer service that processes changes to Flow Spec Store
> --------------------------------------------------------------
>
> Key: GOBBLIN-1705
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1705
> Project: Apache Gobblin
> Issue Type: New Feature
> Components: gobblin-service
> Reporter: Urmi Mustafi
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> In the multi-leader version of GaaS, the REST API layer will not directly
> contact the `GobblinServiceJobScheduler` to respond to API requests. Instead
> after flow level updates are persisted to MySQL, this new monitor will
> subscribe to Kafka events informing it of Flow Spec changes corresponding to
> the API requests and trigger their execution. There will be a similar change
> to follow to respond to other API requests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
