[KYUUBI #6560] Support removing user-specified repartition before writing when using zorder #6561
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔍 Description
Issue References 🔗
This pull request fixes #6560
Describe Your Solution 🔧
RemoveRepartitionBeforeInsertInto
to remove the user-specified repartitionTypes of changes 🔖
Test Plan 🧪
Behavior Without This Pull Request ⚰️
Because the user added unreasonable repartition, the compression rate will not be high enough after turning on zorder, and the overall time consumption will increase significantly.
Behavior With This Pull Request 🎉
After removing the user-specified repartition, the parallelism of Rebalance is more reasonable, resulting in higher compression rate and shorter execution time.
Related Unit Tests
ZorderSuiteBase / test("Check remove user specify repartition as expected")
Checklist 📝
Be nice. Be informative.