[
https://issues.apache.org/jira/browse/CALCITE-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817165#comment-16817165
]
Danny Chan commented on CALCITE-2986:
-------------------------------------
>I am not sure how this will work. Can you provide few examples? What would be
>the transformation for <>ANY in WHERE and <>ANY in SELECT?
I think the <> ANY must be taken into the join condition, and the physical join
must be a NestedLoopJoin, each time the join left side take a loop look up for
the eight side, if left side found there is any right join keys <> the left
keys for the whole right table, it should returns early. Or the whole right
side must be probed.
Whether we translated <> ANY to INNER join or LEFT join is based on if it is in
where clause or project list, which is same as IN.
> Wrong results with =ANY subquery
> --------------------------------
>
> Key: CALCITE-2986
> URL: https://issues.apache.org/jira/browse/CALCITE-2986
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Vineet Garg
> Assignee: Vineet Garg
> Priority: Major
> Labels: pull-request-available, sub-query
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> ANY/SOME subqueries are rewritten using MAX/MIN and cross-join. This is wrong
> transformation for {{=ANY}} and {{<>ANY}} (and therefore {{=ALL}} and
> {{<>ALL}}).
> Query
> {code:sql}
> select * from "scott".emp where empno = any (select empno from "scott".emp);
> {code}
> Expected output for above query is all rows from {{scott.emp}} but actual is
> only one row
> Test case: e.g.
> https://github.com/apache/calcite/compare/master...vineetgarg02:CALCITE-2986
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
