Andrés Taylor
Andrés Taylor
We’re renaming this join strategy to `BlockJoin` to better reflect its general-purpose nature. Initially, we’ll implement only the `VALUES` approach for sending data from the left side to the right....
Updated the description and title to reflect the join name change
I really like this idea! We also want it backported to all supported older versions, so we don't introduce an extra cost for backports.
@derekperkins *bump* given a plan I think this shouldn't be too hard to fix
> I could not find how we improved the planning unless the improvements are in tpch cases. I added a plan to the bottom of `aggr_cases.json`. https://github.com/vitessio/vitess/pull/16278/files#diff-991c94d18be04f57568bac5c003b73009599842b38ee859c489fa286325b9b30R7150 That query produces...
``` │ old.txt │ new.txt │ │ sec/op │ sec/op vs base │ ShardedAggrPushDown/user-100-user_extra-100-10 15.41m ± 6% 16.71m ± 12% +8.41% (p=0.029 n=10) ShardedAggrPushDown/user-100-user_extra-500-10 15.21m ± 3% 15.52m ± 1%...