[
https://issues.apache.org/jira/browse/GOBBLIN-1915?focusedWorklogId=881214&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-881214
]
ASF GitHub Bot logged work on GOBBLIN-1915:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Sep/23 17:17
Start Date: 21/Sep/23 17:17
Worklog Time Spent: 10m
Work Description: homatthew opened a new pull request, #3785:
URL: https://github.com/apache/gobblin/pull/3785
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-XXX
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
The following code
### 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: 881214)
Remaining Estimate: 0h
Time Spent: 10m
> Create a module that depends on Temporal instead of Helix Task Framework
> ------------------------------------------------------------------------
>
> Key: GOBBLIN-1915
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1915
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Matthew Ho
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Helix task framework is slowly fading away as a technology. The industry has
> adopted Temporal as a reliable task framework with good observability, low
> boiler plate, and a theoretical higher throughput. In order to explore this
> technology further, we should create a separate module that is able to spin
> up yarn app master that leverages Temporal instead of Helix TF
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
