planner: support data compression in Broadcast / Passthrough exchange operator; optimize process about choosing Broadcast Join;#41968
Conversation
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
Broadcast / Passthrough exchange operator
|
/retest |
…ompress-bj-exchange
ca6d4ed to
959dce0
Compare
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: c1495a9 |
|
/hold |
|
/hold |
Signed-off-by: Zhigao Tong <tongzhigao@pingcap.com>
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 3ab47aa |
|
/unhold |
|
/test unit-test |
What problem does this PR solve?
Issue Number: ref #40494
What is changed and how it works?
Broadcast/Passthroughexchange operatortidb_prefer_broadcast_join_by_exchange_data_size(release-7.1)tidb_broadcast_join_threshold_sizeandtidb_broadcast_join_threshold_countwill be ignored if planner success to determine whether need broadcast.Benchmark
ENV
Original Threshold x 10: only update threshold about broadcast joinQ8
optimized
Benchmark: One MPP Store
ENV
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.