[HUDI-8400] apply 'write.ignore.failed' when write data failed v2

[fhan688]

Change Logs

In Flink engine, if exception occurs when task writing data, it will be ignored and the exception will be reported to StreamWriteCoordinator with write event, StreamWriteCoordinator will decide whether to commit when there is write failure according to 'write.ignore.failed'.

This PR apply 'write.ignore.failed' ahead when write failure occurs, thus throw an exception faster.

for example:
CP interval of Flink job is 15 minutes, the exception will not be found until CP commit, it will make a longer data latency in real-time sensitive scenarios.

Impact

module: hudi-client、 hudi-flink-datasource

Risk level (write none, low medium or high below)

low

Documentation Update

None

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable
• CI passed

[fhan688]

previous PR was reverted #12136, I reopen it and maybe more discussion is needed. @danny0405

[danny0405]

We should clarify these items:

1. should we promote the write.ignore.failed option to a common write config for each engine? Previously each eagine has it's own options and behavior.
2. should we throw the exception in write handles or in the driver(after the write status are collected);
3. should this option by default false or true?

[danny0405]

Why we throw exception when 'ignore.write.failed' is true?

[fhan688]

We should clarify these items:

1. should we promote the write.ignore.failed option to a common write config for each engine? Previously each eagine has it's own options and behavior.
2. should we throw the exception in write handles or in the driver(after the write status are collected);
3. should this option by default false or true?

1. I agree. write.ignore.failed is a config in FlinkOptions and we promote it to HoodieWriteConfig in hudi-client-common module and named 'hoodie.write.ignore.failed' in this PR.
2. I think fast fail is a better choice. In heavy PRD traffic job, several minutes late means huge amounts of records needs to be dealt with when restore.
3. false, consider data quality.

[hudi-bot]

CI report:

• 7a74ac5 Azure: FAILURE

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build

[danny0405]

@fhan688 Let's fire a JIRA issue around this and move the discussion there.

[fhan688]

OK. https://issues.apache.org/jira/browse/HUDI-8400

[danny0405]

OK. https://issues.apache.org/jira/browse/HUDI-8400

Sorry, I meant the GH issue, which is more easier to communicate.

[fhan688]

OK. https://issues.apache.org/jira/browse/HUDI-8400

Sorry, I meant the GH issue, which is more easier to communicate.

Thanks. #12187