[Enhancement] Reduce fragment plan size #29719
Merged
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.
Fixes #issue
in complex query(a lot of union/expression/select-columns), will make the fragment plan very large.
a
SlotDescriptor
size is 100 byte, 1000+ column will be 100k, so the whole fragment plan reach 1-2MB easily.In x10 BE cluster, a FE's network output bandwidth will reach 10-20MB, and reach 500MB when FE support 50QPS
to handle union sql like:
before:
after:
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: