Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Wed, 18 Jun 2014 19:40:26 +0000 (UTC)
From: "Cheolsoo Park (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12720172.1402340300366.2453.1403120426320@arcas>
In-Reply-To: <JIRA.12720172.1402340300366@arcas>
References: <JIRA.12720172.1402340300366@arcas>
Subject: [jira] [Commented] (PIG-4001) POPartialAgg aggregates too
 aggressively when multiple values aggregated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Cheolsoo Park commented on PIG-4001:
------------------------------------

+1. Will commit this later today.

> POPartialAgg aggregates too aggressively when multiple values aggregated
> ------------------------------------------------------------------------
>
>                 Key: PIG-4001
>                 URL: https://issues.apache.org/jira/browse/PIG-4001
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.13.0
>            Reporter: Travis Woodruff
>            Assignee: Travis Woodruff
>            Priority: Minor
>         Attachments: PIG-4001.patch
>
>
> {{POPartialAgg.aggregateRawRow()}} is counting values in {{numEntriesInTarget}}, but all the values that {{numEntriesInTarget}} is compared to count tuples.
> This is similar to PIG-3649 but has less of a performance impact, as it generally does not cause map-side aggregation to be disabled entirely (since {{aggregateRawRow()}} is unlikely to be called before {{checkSizeReduction()}}; however, it can cause second-level aggregation to be run too often.


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