Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Fri, 1 Nov 2013 18:43:21 +0000 (UTC)
From: "Alex Bain (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12677126.1383331390211.8197.1383331401487@arcas>
In-Reply-To: <JIRA.12677126.1383331390211@arcas>
References: <JIRA.12677126.1383331390211@arcas>
Subject: [jira] [Created] (PIG-3557) Implement optimizations for LIMIT
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Alex Bain created PIG-3557:
------------------------------

             Summary: Implement optimizations for LIMIT
                 Key: PIG-3557
                 URL: https://issues.apache.org/jira/browse/PIG-3557
             Project: Pig
          Issue Type: Bug
          Components: tez
    Affects Versions: tez-branch
            Reporter: Alex Bain
            Assignee: Alex Bain


Implement optimizations for LIMIT when other parts of Pig-on-Tez are more mature. Some of the optimizations mentioned by Daniel include:

1. If the previous stage using 1 reduce, no need to add one more vertex
2. If the limitplan is null (ie, not the "limited order by" case), we might not need a shuffle edge, a pass through edge should be enough if possible
3. Similar to PIG-1270, we can push limit to InputHandler
4. We also need to think through the "limited order by" case once "order by" is implemented


--
This message was sent by Atlassian JIRA
(v6.1#6144)