[
https://issues.apache.org/jira/browse/GOBBLIN-1266?focusedWorklogId=486541&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-486541
]
ASF GitHub Bot logged work on GOBBLIN-1266:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 19/Sep/20 19:24
Start Date: 19/Sep/20 19:24
Worklog Time Spent: 10m
Work Description: sv2000 opened a new pull request #3107:
URL: https://github.com/apache/incubator-gobblin/pull/3107
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-XXX] My Gobblin PR"
- https://issues.apache.org/jira/browse/GOBBLIN-1266
### Description
- [x] Here are some details about my PR, including screenshots (if
applicable):
Dataset Lineage emission in current Gobblin code is only available for batch
mode of execution. For instance, the lineage events are emitted on dataset
commit, which is never invoked for long-running tasks. This PR refactors
lineage related code so that it is leverageable in streaming mode of execution
as well.
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
Existing tests. This PR is purely re-factoring existing code to make it
accessible in other classes.
### 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"
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 486541)
Remaining Estimate: 0h
Time Spent: 10m
> Refactor dataset lineage code to allow Lineage event emission in streaming
> mode
> --------------------------------------------------------------------------------
>
> Key: GOBBLIN-1266
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1266
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-core
> Affects Versions: 0.15.0
> Reporter: Sudarshan Vasudevan
> Assignee: Abhishek Tiwari
> Priority: Major
> Fix For: 0.16.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Dataset Lineage emission in current Gobblin code is only available for batch
> mode of execution. For instance, the lineage events are emitted on dataset
> commit, which is never invoked for long-running tasks. This PR refactors
> lineage related code so that it is leverageable in streaming mode of
> execution as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
