[
https://issues.apache.org/jira/browse/HIVE-26524?focusedWorklogId=826387&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-826387
]
ASF GitHub Bot logged work on HIVE-26524:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Nov/22 04:15
Start Date: 16/Nov/22 04:15
Worklog Time Spent: 10m
Work Description: kasakrisz commented on PR #3753:
URL: https://github.com/apache/hive/pull/3753#issuecomment-1316304825
The `implement` method is never implemented in any of the operators. I
submitted an experimental patch to remove it completely and all PTests passed
#3766
Issue Time Tracking
-------------------
Worklog Id: (was: 826387)
Time Spent: 7.5h (was: 7h 20m)
> Use Calcite to remove sections of a query plan known never produces rows
> ------------------------------------------------------------------------
>
> Key: HIVE-26524
> URL: https://issues.apache.org/jira/browse/HIVE-26524
> Project: Hive
> Issue Type: New Feature
> Components: CBO
> Reporter: Krisztian Kasa
> Assignee: Krisztian Kasa
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-2
>
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> Calcite has a set of rules to remove sections of a query plan known never
> produces any rows. In some cases the whole plan can be removed. Such plans
> are represented with a single {{Values}} operators with no tuples. ex.:
> {code:java}
> select y + 1 from (select a1 y, b1 z from t1 where b1 > 10) q WHERE 1=0
> {code}
> {code:java}
> HiveValues(tuples=[[]])
> {code}
> Other cases when plan has outer join or set operators some branches can be
> replaced with empty values moving forward in some cases the join/set operator
> can be removed
> {code:java}
> select a2, b2 from t2 where 1=0
> union
> select a1, b1 from t1
> {code}
> {code:java}
> HiveAggregate(group=[{0, 1}])
> HiveTableScan(table=[[default, t1]], table:alias=[t1])
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
