[
https://issues.apache.org/jira/browse/CALCITE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-444.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.9.2-incubating
Fixed in
http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/e4fcf2a3.
> Filters wrongly pushed into full outer join
> -------------------------------------------
>
> Key: CALCITE-444
> URL: https://issues.apache.org/jira/browse/CALCITE-444
> Project: Calcite
> Issue Type: Bug
> Reporter: Laljo John Pullokkaran
> Assignee: Laljo John Pullokkaran
> Fix For: 0.9.2-incubating
>
> Attachments: CALCITE-444.1.patch, CALCITE-444.patch
>
>
> Filter R1.x=10 (R1 full outer join R2 on R1.y=R2.y)
> Gets rewritten as
> R1 left outer join R2 on R1.y=R2.y and R1.x=10.
> This is obviously wrong and produces wrong result.
> select count(*) from(select ss.ss_sold_date_sk, ss.ss_item_sk,
> ss.ss_customer_sk from store_sales ss full outer join date_dim d on
> ss.ss_sold_date_sk = d.d_date_sk where ss.ss_item_sk = 4496)R;
> produces wrong result due to above described problem.
> Patch separates the join simplification from Join filter classification.
> Predicate Push Down through Join would first simplify Outer Joins before
> applying predicate push down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
