[
https://issues.apache.org/jira/browse/GOBBLIN-1565?focusedWorklogId=669808&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-669808
]
ASF GitHub Bot logged work on GOBBLIN-1565:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Oct/21 21:32
Start Date: 25/Oct/21 21:32
Worklog Time Spent: 10m
Work Description: ZihanLi58 opened a new pull request #3419:
URL: https://github.com/apache/gobblin/pull/3419
…e will not affect other topics in the same container
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-1565
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
GMIP should be fault tolerant, so that one topic failure should not affect
other topics in the same container. One potential solution is that we can catch
the error and document the error dataset, if we have more than one datasets
have issue, that normally something wrong happening on the whole job, we should
fail the task, but if there is only one problematic topic, we can handle the
exception and let the pipeline move on and process other topics.
Left some todo for emitting GTE so that we can rely on those event to detect
failure and do backfill as needed
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
Add new unit test
### 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]
Issue Time Tracking
-------------------
Worklog Id: (was: 669808)
Remaining Estimate: 0h
Time Spent: 10m
> Make GMCEWriter fault tolerant so that one topic failure will not affect
> other topics in the same container
> -----------------------------------------------------------------------------------------------------------
>
> Key: GOBBLIN-1565
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1565
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Zihan Li
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> GMIP should be fault tolerant, so that one topic failure should not affect
> other topics in the same container. One potential solution is that we can
> catch the error and document the error dataset, if we have more than one
> datasets have issue, that normally something wrong happening on the whole
> job, we should fail the task, but if there is only one problematic topic, we
> can handle the exception and let the pipeline move on and process other
> topics.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
