[
https://issues.apache.org/jira/browse/GOBBLIN-1705?focusedWorklogId=807572&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-807572
]
ASF GitHub Bot logged work on GOBBLIN-1705:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Sep/22 19:35
Start Date: 09/Sep/22 19:35
Worklog Time Spent: 10m
Work Description: umustafi commented on code in PR #3557:
URL: https://github.com/apache/gobblin/pull/3557#discussion_r967405152
##########
gobblin-service/src/main/java/org/apache/gobblin/service/modules/core/GobblinServiceConfiguration.java:
##########
@@ -70,6 +70,9 @@ public class GobblinServiceConfiguration {
@Getter
private final boolean isHelixManagerEnabled;
+ @Getter
+ private final boolean isSpecStoreChangeMonitorEnabled;
Review Comment:
I was thinking that as well because we do not one turned on without the
other. However neither the `warmStandbyEnabled` or
`specStoreChangeMonitorEnabled` terms encapsulate all the multi-leader mode
changes as a whole. I can create a configuration key `multiLeaderModeEnabled`
which we can use in both places. What do you think?
Issue Time Tracking
-------------------
Worklog Id: (was: 807572)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
