[Cherry Pick] Join enhancements and HLL type inference bug fix #16
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:
Cherry-picking PR - StarRocks#52021 from the main StarRocks branch to improve data distribution prior to joins in certain queries. More specifically, this issue was observed when profiling two very similar queries whose latencies were drastically different although joining on the same data. Upon investigation the faster query was distributed across more nodes going into a hash join operator. This should help improve data distribution prior to joins resolving the latency inconsistency.
Cherry-picking PR - StarRocks#51510 from the main StarRocks branch to resolve a type inference bug discovered when performing a union across two HLL typed columns across two distinct tables.
What I'm doing:
Cherry-picking PR - StarRocks#52021 and Cherry-picking PR - StarRocks#51510
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: