-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HUDI-8881] trigger failure earlier in Flink Hudi sink #12666
base: master
Are you sure you want to change the base?
[HUDI-8881] trigger failure earlier in Flink Hudi sink #12666
Conversation
6194d60
to
d04b0f1
Compare
2d91da4
to
5333ece
Compare
...datasource/hudi-flink/src/main/java/org/apache/hudi/sink/StreamWriteOperatorCoordinator.java
Outdated
Show resolved
Hide resolved
@@ -473,6 +475,19 @@ private void handleEndInputEvent(WriteMetadataEvent event) { | |||
} | |||
} | |||
|
|||
private void filterWriteFailure(WriteMetadataEvent event) throws HoodieException { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we reuse the same logic in doCommit method as well to prevent any future logical divergence in detecting write failures?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a good suggestion. The logical of detecting write failures is actually one single line with stream API. I feel it is overkill to create a separate function for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@danny0405 Do you think we also need to log error in single event as commit time?
5333ece
to
3112505
Compare
Change Logs
Trigger failure when write failure is detected for flink hudi sink
Impact
The early detection of write failure will prevent checkpoint to complete before hudi commit. Thus, prevent the data loss when checkpoint is completed, but hudi can't committed due the write failure.
Risk level (write none, low medium or high below)
none
Documentation Update
It is an improvement of existing functionality, no user facing feature is introduced.
Contributor's checklist