You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2014/12/30 16:45:13 UTC

[jira] [Resolved] (CALCITE-451) Implement theta join, inner and outer, in enumerable convention

     [ https://issues.apache.org/jira/browse/CALCITE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-451.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0-incubating

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/167623f4.

> Implement theta join, inner and outer, in enumerable convention
> ---------------------------------------------------------------
>
>                 Key: CALCITE-451
>                 URL: https://issues.apache.org/jira/browse/CALCITE-451
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>             Fix For: 1.0.0-incubating
>
>
> Implement theta join in enumerable convention. It must handle not just equi-, or equi-plus-theta (see CALCITE-371) but any join condition. It must also handle inner and all types of outer join.
> Performance may not be that good. Other join algorithms (e.g. hash join,  nested loops doing range scans into a sorted map, or merge joins) can offer better alternatives for particular operators (e.g. {{BETWEEN}}).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)