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

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

GitHub user sirpkt opened a pull request:

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

    TAJO-1514: Distinguish UNION and UNION ALL

    This patch distinguishes UNION and UNION ALL, and implements UNION as UNION 
ALL + GROUP BY
    
    UNION logical node with distinct flag is written as
    Projection + Group by + Table Subquery + Union
    
    It also fix test queries wrongly use union like union all
    
    'mvn clean install' passed in my laptop

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

    $ git pull https://github.com/sirpkt/tajo TAJO-1514

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

    https://github.com/apache/tajo/pull/505.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 #505
    
----
commit 337919d03c1b7b152b38afdaf9aa799f6440adb2
Author: Keuntae Park <[email protected]>
Date:   2015-04-03T07:39:41Z

    This patch distinguishes UNION and UNION ALL, and implements UNION as UNION 
ALL + GROUP BY
    
    UNION logical node with distinct flag is written as
    Projection + Group by + Table Subquery + Union
    
    It also fix test queries wrongly use union like union all
    
    'mvn clean install' passed in my laptop

----


> Distinguish UNION and UNION ALL
> -------------------------------
>
>                 Key: TAJO-1514
>                 URL: https://issues.apache.org/jira/browse/TAJO-1514
>             Project: Tajo
>          Issue Type: Sub-task
>            Reporter: Keuntae Park
>            Assignee: Keuntae Park
>
> Currently, Tajo handles both UNION and UNION ALL as UNION ALL.
> For UNION, however, result should not have duplicated rows.
> It needs to handle them differently.  



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

Reply via email to