You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/09/01 17:20:00 UTC
[jira] [Work logged] (GOBBLIN-1696) Build a file-based flowgraph that watches for changes and updates
[ https://issues.apache.org/jira/browse/GOBBLIN-1696?focusedWorklogId=805594&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-805594 ]
ASF GitHub Bot logged work on GOBBLIN-1696:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/Sep/22 17:19
Start Date: 01/Sep/22 17:19
Worklog Time Spent: 10m
Work Description: Will-Lo opened a new pull request, #3548:
URL: https://github.com/apache/gobblin/pull/3548
… filesystem and updates dynamically
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
- [ ] 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-1696
### Description
- [x] Here are some details about my PR, including screenshots (if applicable):
Gobblin-as-a-Service only has a Git based flowgraph, which is difficult to build CI/CD around.
This is an alternate flowgraph that watches for file changes and applies updates.
Unlike the git based flowgraph, changes in this flowgraph are atomic with respect to one deployment of the flowgraph, which is an update of multiple files.
This also requires an enhancement to the PathAlterationObserver to notify listeners if there is any change on a root level.
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
### 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: 805594)
Remaining Estimate: 0h
Time Spent: 10m
> Build a file-based flowgraph that watches for changes and updates
> -----------------------------------------------------------------
>
> Key: GOBBLIN-1696
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1696
> Project: Apache Gobblin
> Issue Type: New Feature
> Components: gobblin-service
> Reporter: William Lo
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Gobblin-as-a-Service only has a Git based flowgraph, which is difficult to build CI/CD around. We can provide an alternate flowgraph that is just based off files. This flowgraph should update atomically.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)