Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Wed, 12 Aug 2015 23:56:45 +0000 (UTC)
From: "Rohini Palaniswamy (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12855727.1439423772000.51103.1439423805756@Atlassian.JIRA>
In-Reply-To: <JIRA.12855727.1439423772000@Atlassian.JIRA>
References: <JIRA.12855727.1439423772000@Atlassian.JIRA>
 <JIRA.12855727.1439423772583@arcas>
Subject: [jira] [Created] (PIG-4657) [Pig on Tez] Optimize GroupBy and
 Distinct key comparison
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Rohini Palaniswamy created PIG-4657:
---------------------------------------

             Summary: [Pig on Tez] Optimize GroupBy and Distinct key comparison
                 Key: PIG-4657
                 URL: https://issues.apache.org/jira/browse/PIG-4657
             Project: Pig
          Issue Type: Sub-task
            Reporter: Rohini Palaniswamy
            Assignee: Rohini Palaniswamy
             Fix For: 0.16.0


   While bytes comparator cannot be used for joins till TEZ-2715 is available, they can be used for group by and distinct if they have only one Tez input. If there is more than one input due to union optimization (OrderedGroupedMergedKVInput) , full comparator has to be still used as OrderedGroupedMergedKVInput uses the comparator to merge the two underlying inputs.


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