You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Alex Bain (JIRA)" <ji...@apache.org> on 2014/01/16 01:45:22 UTC
[jira] [Updated] (PIG-3557) Implement optimizations for LIMIT
[ https://issues.apache.org/jira/browse/PIG-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Bain updated PIG-3557:
---------------------------
Attachment: PIG-3557.patch
> Implement optimizations for LIMIT
> ---------------------------------
>
> Key: PIG-3557
> URL: https://issues.apache.org/jira/browse/PIG-3557
> Project: Pig
> Issue Type: Sub-task
> Components: tez
> Affects Versions: tez-branch
> Reporter: Alex Bain
> Assignee: Alex Bain
> Attachments: PIG-3557.patch
>
>
> 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.5#6160)