[
https://issues.apache.org/jira/browse/PIG-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751950#comment-13751950
]
Daniel Dai commented on PIG-3435:
---------------------------------
custom-partitioner + multiquery optimization should be a valid use case, we
shall open a Jira ticket for it.
But correctness first, +1 for the patch.
> Custom Partitioner not working with MultiQueryOptimizer
> -------------------------------------------------------
>
> Key: PIG-3435
> URL: https://issues.apache.org/jira/browse/PIG-3435
> Project: Pig
> Issue Type: Bug
> Components: impl
> Reporter: Koji Noguchi
> Assignee: Koji Noguchi
> Attachments: pig-3435-v01.patch,
> pig-3435-v02_skipcustompatitioner_for_merge.patch
>
>
> When looking at PIG-3385, noticed some issues in handling of custom
> partitioner with multi-query optimization.
> {noformat}
> C1 = group B1 by col1 PARTITION BY
> org.apache.pig.test.utils.SimpleCustomPartitioner parallel 2;
> C2 = group B2 by col1 PARTITION BY
> org.apache.pig.test.utils.SimpleCustomPartitioner parallel 2;
> {noformat}
> This seems to be merged to one mapreduce job correctly but custom partitioner
> information was lost.
> {noformat}
> C1 = group B1 by col1 PARTITION BY
> org.apache.pig.test.utils.SimpleCustomPartitioner parallel 2;
> C2 = group B2 by col1 parallel 2;
> {noformat}
> This seems to be merged even though they should run on two different
> partitioner.
--
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
