[
https://issues.apache.org/jira/browse/GOBBLIN-1910?focusedWorklogId=880528&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-880528
]
ASF GitHub Bot logged work on GOBBLIN-1910:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Sep/23 21:49
Start Date: 14/Sep/23 21:49
Worklog Time Spent: 10m
Work Description: 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"
Issue Time Tracking
-------------------
Worklog Id: (was: 880528)
Remaining Estimate: 0h
Time Spent: 10m
> Refactor code to move current in-memory references to new design for REST
> calls: Launch, Resume and Kill
> --------------------------------------------------------------------------------------------------------
>
> Key: GOBBLIN-1910
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1910
> Project: Apache Gobblin
> Issue Type: New Feature
> Reporter: Meeth Gala
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
