[
https://issues.apache.org/jira/browse/GOBBLIN-1673?focusedWorklogId=802191&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-802191
]
ASF GitHub Bot logged work on GOBBLIN-1673:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 20/Aug/22 03:45
Start Date: 20/Aug/22 03:45
Worklog Time Spent: 10m
Work Description: homatthew opened a new pull request, #3539:
URL: https://github.com/apache/gobblin/pull/3539
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-1683] My Gobblin PR"
- https://issues.apache.org/jira/browse/GOBBLIN-1683
- https://issues.apache.org/jira/browse/GOBBLIN-1673
### Description
- [X] Here are some details about my PR, including screenshots (if
applicable):
The Dynamic work unit project is to enable gobblin streaming to modify the
workunits from a source after the pipeline has started.
In order to do this, the task runner must communicate its current state back
to the application master. This PR describes the data schema for communication
and provides the skeleton code for the AM and gobblin task runner to
communicate.
### Tests
- [X] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
Unit tests added for serialization. No UT's added for interfaces because
they are interfaces. No UT added for the background thread method since that is
not an easy to test method.
### 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: 802191)
Remaining Estimate: 71h 50m (was: 72h)
Time Spent: 10m
> [Helix Dynamic Workunit] Message Schema for splitting workuntis
> ---------------------------------------------------------------
>
> Key: GOBBLIN-1673
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1673
> Project: Apache Gobblin
> Issue Type: New Feature
> Components: gobblin-helix
> Reporter: Matthew Ho
> Assignee: Abhishek Tiwari
> Priority: Major
> Original Estimate: 72h
> Time Spent: 10m
> Remaining Estimate: 71h 50m
>
> For the Helix Dynamic Workunits, task runners will produce messages
> indicating the current workunit health and the application master will
> consume these messages.
> A message will be sent from the task runner to the AM when the task runner
> experiences lag during ingestion. This ticket is the schema proposal for this
> message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
