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

Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2014/02/24 12:40:19 UTC

[jira] [Commented] (TAJO-628) The second stage of distinct aggregation can be scheduled to only one node.

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

Hyunsik Choi commented on TAJO-628:
-----------------------------------

Created a review request against branch master in reviewboard 
https://reviews.apache.org/r/18420/


> The second stage of distinct aggregation can be scheduled to only one node.
> ---------------------------------------------------------------------------
>
>                 Key: TAJO-628
>                 URL: https://issues.apache.org/jira/browse/TAJO-628
>             Project: Tajo
>          Issue Type: Bug
>          Components: distributed query plan
>    Affects Versions: 0.8-incubating, 1.0-incubating
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>            Priority: Minor
>         Attachments: TAJO-628.patch
>
>
> Distinct aggregation requires three stages. But, the second stage can be scheduled to one node due to wrong counting of grouping keys.
> This patch fixes this bug. In addition, this patch fixes some trivial bugs in Task.java that I found during this debugging.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)