Hi Boaz:
Sorry for the wrong example. "select t2.a,t2.s,t3.d (select a, sum(b) as
s from t1 where c='1' group by a ) t2 join t3 on t2.a = t3.a" this sql
would make sense.
The prerequisite for join push down is the storage plugin supports filter
push down. The corresponding rule should
Hi Boaz:
Sorry for the wrong example,it should be
"select t2.a,t2.s,t3.d (select a, sum(b) as s from t1 where c='1' group by
a ) t2 join t3 on t2.a = t3.a" which would make sense.
The prerequisite for pushing down join is the storage plugin support filter
push down. The storage plugin should
Hi Weijie,
Are there some typos in the sample query ? Looks like the projection
should be t2.a,t2.s,t3.d (i.e., t2 instead of t1). Also the predicate “ where
a='1' ” makes the inner query return only a single row, which is pretty trivial.
Assuming these changes are made, then there
All:
This is a propose about join query tuning by pushing down the join
condition. Welcome suggestion ,discussion,objection .
Suppose we have a join query "select t1.a,t1.s,t3.d (select a, sum(b) as
s from t1 where a='1' group by a ) t2 join t3 on t2.a = t3.a" . This
query will be
