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

   ### Change Logs
   
   - Previously the log files were associated with the latest base file at the 
time the commit starts. Since compaction planning or a successful compaction 
causes a new base file, we need to check for conflicts with compaction for 
these older table versions. 
   - Starting with table version 8, the log files are associated with a base 
file based on the completion time so we don't rely on the current state of a 
file group when creating these log files. That means we no longer need to check 
compaction for conflicts which in turn allows for smoother operations on MoR 
tables.
   
   ### Impact
   
   - Allows async compaction to schedule and run without causing disruption to 
other writers
   
   ### Risk level (write none, low medium or high below)
   
   High, this is a core change to conflict detection. 
   
   ### 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](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