[jira] [Commented] (TAJO-891) Complex join conditions with UNION or inline should be supported

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAJO-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048756#comment-14048756 ] 

ASF GitHub Bot commented on TAJO-891:
-------------------------------------

Github user jinossy commented on the pull request:

    https://github.com/apache/tajo/pull/49#issuecomment-47642574
  
    +1 
    Looks great!  I've verified 'mvn clean install'.


> Complex join conditions with UNION or inline should be supported
> ----------------------------------------------------------------
>
>                 Key: TAJO-891
>                 URL: https://issues.apache.org/jira/browse/TAJO-891
>             Project: Tajo
>          Issue Type: Bug
>          Components: distributed query plan, planner/optimizer
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.9.0
>
>
> Please see the following two example queries. Currently, they will cause planning exception. This patch fixes the bugs.
> {code}
> select
>   n1.n_nationkey,
>   substr(n1.n_name, 1, 4) name1,
>   substr(n2.n_name, 1, 4) name2
> from nation n1 join (select * from nation) n2 on substr(n1.n_name, 1, 4) = substr(n2.n_name, 1, 4)
> order by n1.n_nationkey;
> {code}
> {code}
> select
>   n1.n_nationkey,
>   substr(n1.n_name, 1, 4) name1,
>   substr(n2.n_name, 1, 4) name2
> from nation n1 join (select * from nation union select * from nation) n2 on substr(n1.n_name, 1, 4) = substr(n2.n_name, 1, 4)
> order by n1.n_nationkey;
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)