meethngala opened a new pull request, #3776: URL: https://github.com/apache/gobblin/pull/3776
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-1910 ### Description - [ ] Here are some details about my PR, including screenshots (if applicable): I am creating this PR as part of refactoring the DagManager to make it less bulky and eventually stateless (after getting rid of the in-memory references). This PR is only handling the cases for adhoc REST client calls for launch, resume and kill/cancel flows. Currently, this PR is only providing a template for the end-to-end functionality and implementing some parts of existing DagManager's responsibility. There will be subsequent PRs to implement functionalities that are missing likewise scheduler triggers via orchestrator, advancing to the next set of nodes in a Dag, cleaning up of Dags etc. The method signatures, instantiations and return types use widely accepted and default values, but will be restricted once responsibility/functionality of each class is determined. ### Tests - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: ### Commits - [ ] 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" -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
