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

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

GitHub user babokim opened a pull request:

    https://github.com/apache/tajo/pull/50

    TAJO-894: Left outer join with partitioned large table and small table 
returns empty result.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/babokim/tajo TAJO-894

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tajo/pull/50.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 #50
    
----
commit 57bcd37bf2e7c3f3e9739d56ab63ba78b2bcd310
Author: 김형준 <[email protected]>
Date:   2014-06-30T01:06:41Z

    TAJO-894: Left outer join with partitioned large table and small table 
returns empty result.

----


> Left outer join with partitioned large table and small table returns empty 
> result.
> ----------------------------------------------------------------------------------
>
>                 Key: TAJO-894
>                 URL: https://issues.apache.org/jira/browse/TAJO-894
>             Project: Tajo
>          Issue Type: Bug
>            Reporter: Hyoungjun Kim
>            Assignee: Hyoungjun Kim
>            Priority: Minor
>
> Left outer join with a small table and a large partitioned table which not 
> matched any partition path returns empty result .
> If there is no partitioned path with l_orderkey = 1000 in the lineitem_large, 
> the following query should return all records which lineitem_small table has 
> but return empty record.
> {code:sql}
> select a.l_orderkey as key1, b.l_orderkey as key2 
> from lineitem_small as a 
> left outer join lineitem_large as b
> on a.l_partkey = b.l_partkey and b.l_orderkey = 1000
> {code}



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

Reply via email to