[HUDI-8605] Fix Trino failure when reading corrupted block at end of log file

[usberkeley]

Change Logs

Background

When a corrupted block appears at the end of a Log file, the Trino Reader (LogScanner) fails to read it. This is because Hudi attempts to use InputStream#seek to locate the end of the LogBlock to check for corruption. However, Trino's TrinoInputStream#seek does not necessarily throw an EOFException when seeking beyond the end of the file. In some file systems, such as AzureInputStream#seek and so on, it may throw an IOException, not an EOFException.

Why do we need this PR ?

The Trino issue is not unique, we might encounter custom InputStreams that encapsulate their own exception classes in reader. Therefore, we compare the position obtained from InputStream#getPos with the file length to determine if the end of the file has been reached

Impact

Fix Trino failure when reading corrupted block at end of log file

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

[hudi-bot]

CI report:

• d73a7eb UNKNOWN
• f826fc8 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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

[yihua]

@voonhous could you review this?