[HUDI-7549] Reverting spurious log block deduction with LogRecordReader

[nsivabalan]

Change Logs

We added support to deduce spurious log blocks with log block reader (https://github.com/apache/hudi/pull/9545 and https://github.com/apache/hudi/pull/9611 ) in 0.14.0. Apparently there are some cases where it could lead to data loss or data consistency issues. https://github.com/apache/hudi/pull/9611#issuecomment-2016687160 So, we are reverting the changes for now until we have a thorough patch where we can deduce such spurious log blocks.

Impact

No data consistency issues w/ log record reader.

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

medium

Documentation Update

Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

• The config description must be updated if new configs are added or the default value of the configs are changed
• Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the ticket number here and follow the instruction to make changes to the website.

Contributor's checklist

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

[yihua]

@nsivabalan could you check the CI failures?

[hudi-bot]

CI report:

• 802eeb74510ddbeb5cd952d9192aaf623d9c7ee9 Azure: PENDING

Bot commands

@hudi-bot supports the following commands:

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

[yihua]

Azure CI is green.