[
https://issues.apache.org/jira/browse/GOBBLIN-1419?focusedWorklogId=584480&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-584480
]
ASF GitHub Bot logged work on GOBBLIN-1419:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Apr/21 20:04
Start Date: 16/Apr/21 20:04
Worklog Time Spent: 10m
Work Description: ZihanLi58 opened a new pull request #3255:
URL: https://github.com/apache/gobblin/pull/3255
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-1419
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
No compaction publish file and emit GMCE are happening separately. If file
rename succeed but emit GMCE fails, we will end up with not emit GMCE for the
compaction. So need a strategy to do error handling for compaction that when
emit GMCE fails, next job will treat the previous compaction as fail and
re-compact the data.
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 584480)
Time Spent: 1h 10m (was: 1h)
> Error handling for compaction pipeline on GMCE emitted error
> ------------------------------------------------------------
>
> Key: GOBBLIN-1419
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1419
> Project: Apache Gobblin
> Issue Type: Task
> Reporter: Zihan Li
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> No compaction publish file and emit GMCE are happening separately. If file
> rename succeed but emit GMCE fails, we will end up with not emit GMCE for the
> compaction. So need a strategy to do error handling for compaction that when
> emit GMCE fails, next job will treat the previous compaction as fail and
> re-compact the data.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
