[HUDI-6979][RFC-76] support event time based compaction strategy
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. low
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks. low
Documentation Update
none
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 to make changes to the website.
Contributor's checklist
- [ ] Read through contributor's guide
- [ ] Change Logs and Impact were stated clearly
- [ ] Adequate tests were added if applicable
- [ ] CI passed
@waitingF Might need to update the RFC claim number as these RFC-74 and RFC-75 were claimed recently under this PR
https://github.com/apache/hudi/pull/10275