yihua opened a new pull request, #10575:
URL: https://github.com/apache/hudi/pull/10575

   ### Change Logs
   
   This PR introduces `SeekableDataInputStream` for random access on a file, 
i.e., seeking to a position in a file and reading the content.  The random 
access on a file is used by the log scanner and reader.  Before this PR, the 
log reader relies on `FSDataInputStream` which is coupled with Hadoop file 
system.  To allow Hadoop-independent file systems to be used to read log files, 
the interface `SeekableDataInputStream` is introduced to provide random access 
APIs without relying on `FSDataInputStream`.
   
   This is part of the effort to provide Hudi storage abstraction and decouple 
`hudi-common` from hadoop dependencies. For reference, the single big-change PR 
can be found here: #10360.
   ### Impact
   
   _Describe any public API or user-facing feature change or any performance 
impact._
   
   ### Risk level (write none, low medium or high below)
   
   _If medium or high, explain what verification was done to mitigate the 
risks._
   
   ### Documentation Update
   
   _Describe any necessary documentation update if there is any new feature, 
config, or user-facing change_
   
   - _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](https://hudi.apache.org/contribute/developer-setup#website) to 
make
     changes to the website._
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Change Logs and Impact were stated clearly
   - [ ] Adequate tests were added if applicable
   - [ ] CI passed
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to