[Enhancement] Optimize MaterializedView's inferDistribution policy by using existing tablets (backport #63367) #63728
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.
Why I'm doing:
#26726 may create mv with many buckets(200/500) if there are many compute nodes(eg: 30) which will cause the culster unstable because of huge metadata in FE.
The current implementation hasn't taken
hash/random
distribution yet and may generate too many tablets:What I'm doing:
Use OlapTable's implementation (#38763) to deduce mv's default bucket by default.
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #63367 done by [Mergify](https://mergify.com).