You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Koji Noguchi (JIRA)" <ji...@apache.org> on 2013/08/28 03:16:52 UTC

[jira] [Assigned] (PIG-3440) MultiQuery to work with custom partitioner

     [ https://issues.apache.org/jira/browse/PIG-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koji Noguchi reassigned PIG-3440:
---------------------------------

    Assignee: Koji Noguchi

Taking a look.  I'm not sure if we should limit the merging to jobs with same custom partitioners or 
if we can merge all jobs and have single partitioner that delegates to the corresponding partitioner based on inputs.

(I'm still learning multi-query optimization.  I may be off on this.)
                
> MultiQuery to work with custom partitioner
> ------------------------------------------
>
>                 Key: PIG-3440
>                 URL: https://issues.apache.org/jira/browse/PIG-3440
>             Project: Pig
>          Issue Type: Bug
>          Components: impl
>            Reporter: Daniel Dai
>            Assignee: Koji Noguchi
>
> Currently Pig disable multiquery in case of custom partitioner in PIG-3435. However, when custom partitioner are the same, we can still use multiquery. This is the Jira ticket to track this optimization.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira