[
https://issues.apache.org/jira/browse/TAJO-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044540#comment-14044540
]
ASF GitHub Bot commented on TAJO-891:
-------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/49
TAJO-891: Complex join conditions with UNION or inline should be support...
...ed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-891
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/49.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #49
----
commit 83b5eb12f79502cff370539f7e9dd3308f049d33
Author: Hyunsik Choi <[email protected]>
Date: 2014-06-26T10:11:20Z
TAJO-891: Complex join conditions with UNION or inline should be supported.
----
> 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)
