zhuanshenbsj1 opened a new pull request, #8395:
URL: https://github.com/apache/hudi/pull/8395
### Change Logs
1. Insert scenario in the COW table, if both online sync-clustering and
online async-clustering(plan generate || plan execute) are configured
simultaneously, sometimes sync-clustering takes effect, sometimes
async-clustering takes effect：
sync-clustering=true & generate async-clustering=true & execute
async-clustering=true：sync-clustering takes effect
sync-clustering=true & generate async-clustering=false & execute
async-clustering=true: async-clustering takes effect
3. Insert scenario in the MOR table，sometimes generate log files, sometimes
generate parquet files.
async-compaction=true & generate async-clustering=false : generate log files
async-compaction=false & generate async-clustering=true: generate parquet
files
This will cause confusion for users
After modification:
1. Insert scenario in the COW table, sync-clustering has higher priority
than online async-clusering.
3. Insert scenario in the MOR table will always generate parquet files
### 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]
