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

   ### Change Logs
   
   Currently, to gain low ingestion latency, we can adopt the MergeOnRead 
table, which support appending log files and 
   compact log files into base file later. When querying the snapshot table (RT 
table) generated by MOR, 
   query side have to perform a compaction so that they can get all data, which 
is expected time-consuming causing query latency.
   At the time, hudi provide read-optimized table (RO table) for low query 
latency just like COW.
   
   But currently, there is no compaction strategy based on event time, so there 
is no data freshness guarantee for RO table.
   For cases, user want all data before a specified time, user have to query 
the RT table to get all data with expected high query latency.
   
   Based on this, we want to implement the strategy based on the event time: 
`EventTimeBasedCompactionStrategy`. 
   
   ### 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