You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In relation to #2203 which added support for explicit join tree syntax there is still a problem with slightly more complex queries, hinting at an underlying problem.
When executing the following script:
createtablet(x int, y int, z int);
select*from t
left join (t t1 join t t2 ont1.y=t2.y) ont1.y=t.yleft join (t t3 join t t4 ont3.xis not null) ont3.z=t.z
;
There is an error [HY000][1105] table "t3" does not have column "x" where x apparently refers to the t3.x reference in the last line.
What is interesting is that if the first JOIN is removed then the query is executed successfully. Also when changing the join predicate from t3.x is not null to e.g. t3.x = t4.x there is no problem.
The text was updated successfully, but these errors were encountered:
When a join condition is specific to a single table, we hoist the filter for later pushdown. Our condition for filter placement accidentally moved the filter to every child of the join's parent. It works when you change the IS NULL because we can't hoist the filter. It works when you remove the parent join because then there is no sibling node that absorbs a filter it doesn't know how to execute.
In relation to #2203 which added support for explicit join tree syntax there is still a problem with slightly more complex queries, hinting at an underlying problem.
When executing the following script:
There is an error
[HY000][1105] table "t3" does not have column "x"
wherex
apparently refers to thet3.x
reference in the last line.What is interesting is that if the first
JOIN
is removed then the query is executed successfully. Also when changing the join predicate fromt3.x is not null
to e.g.t3.x = t4.x
there is no problem.The text was updated successfully, but these errors were encountered: