Re: [I] Fix EOF exception in Trino reader when reading log files [hudi]

["rangareddy (via GitHub)" <gi...@apache.org>]

rangareddy commented on issue #16122:
URL: https://github.com/apache/hudi/issues/16122#issuecomment-4890000121

   This issue was reviewed as part of the JIRA-migrated backlog triage.
   
   Findings: valid issue. When a corrupted block sits at the end of a log file, seek-based EOF detection can throw an IOException instead of EOFException on Trino / some cloud filesystems (e.g. Azure), breaking the log reader. A fix was proposed in #12237 (compare log-block end position against file end) but that PR was closed unmerged and no alternate fix has landed on master.
   
   Fix scope is larger than a local patch and requires re-landing the log-block boundary check. Tracking as `stream:fix / read_path`.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org