Vitalii Diravka created DRILL-6371:
--------------------------------------
Summary: Use FilterSetOpTransposeRule,
DrillProjectSetOpTransposeRule in main logical stage
Key: DRILL-6371
URL: https://issues.apache.org/jira/browse/DRILL-6371
Project: Apache Drill
Issue Type: Improvement
Components: Query Planning & Optimization
Affects Versions: 1.13.0
Reporter: Vitalii Diravka
Fix For: Future
FilterSetOpTransposeRule, DrillProjectSetOpTransposeRule are leveraged in
DRILL-3855.
They are used in HepPlanner, but if they additionally will be enabled in main
logical planning stage for Volcano planner, more cases will be covered with
these rules.
For example:
{code}
WITH year_total_1
AS (SELECT c.r_regionkey customer_id,
1 year_total
FROM cp.`tpch/region.parquet` c
UNION ALL
SELECT c.n_nationkey customer_id,
1 year_total
FROM cp.`tpch/nation.parquet` c),
year_total_2
AS (SELECT c.r_regionkey customer_id,
1 year_total
FROM cp.`tpch/region.parquet` c
UNION ALL
SELECT c.n_nationkey customer_id,
1 year_total
FROM cp.`tpch/nation.parquet` c)
SELECT count(t_w_firstyear.customer_id) as ct
FROM year_total_1 t_w_firstyear,
year_total_2 t_w_secyear
WHERE t_w_firstyear.year_total = t_w_secyear.year_total
AND t_w_firstyear.year_total > 0 and t_w_secyear.year_total > 0
{code}
Currently using them in Volcano Planner can cause infinite loops - CALCITE-1271
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
