[
https://issues.apache.org/jira/browse/GOBBLIN-1705?focusedWorklogId=807230&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-807230
]
ASF GitHub Bot logged work on GOBBLIN-1705:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Sep/22 00:17
Start Date: 09/Sep/22 00:17
Worklog Time Spent: 10m
Work Description: umustafi opened a new pull request, #3557:
URL: https://github.com/apache/gobblin/pull/3557
* enabled by configuration for now
* the monitor processes changes to specs due to API requests and notifies
the Scheduler to execute actions
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I
have checked off all the steps below!
### JIRA
- [X] My PR addresses the following [Gobblin
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
- https://issues.apache.org/jira/browse/GOBBLIN-1705
### Description
- [X] Here are some details about my PR, including screenshots (if
applicable):
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.
### Tests
- [X] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
No testing added for now as it should be tested end to end with actual Kafka
events
### Commits
- [X] My commits all reference JIRA issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not "adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
Issue Time Tracking
-------------------
Worklog Id: (was: 807230)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)
