the-other-tim-brown opened a new pull request, #9337:
URL: https://github.com/apache/hudi/pull/9337

   ### Change Logs
   
   - Updates sections of the code to use the getters in the HoodieBaseFile and 
HoodieLogFile instead of FSUtils to move away from relying directly on the path 
for getting metadata about the file when possible
   - Sets file ID and commit time in HoodieBaseFile on construction and avoids 
running `split` on the file name twice to improve efficiency
   - Sets fileId, baseCommitTime, logVersion, logWriteToken, fileExtension, 
suffix, and path when creating HoodieLogFile instead of making multiple calls 
to a regex based matcher to improve efficiency
   - Uses CachingPath instead of Path in HoodieLogFile for improved efficiency
   
   ### Impact
   
   Lowers overhead when extracting metadata about HoodieBaseFiles or 
HoodieLogFiles
   
   ### Risk level (write none, low medium or high below)
   
   low, unit tests were added to assert behavior is maintained 
   
   ### 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: commits-unsubscr...@hudi.apache.org

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

Reply via email to