[
https://issues.apache.org/jira/browse/PIG-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948100#comment-13948100
]
Rohini Palaniswamy commented on PIG-3743:
-----------------------------------------
bq. In addition, can we fix the skew first
How bad is the performance regression? Are you asking for committing
PIG-3743-fix-skew.patch and then address POValueOuputTez in a separate jira? I
don't have a problem with that. Can probably be clubbed with PIG-3835.
Also for POValueOuputTez instead of implementing WritableComparable it would be
better to write a custom Comparator and either return 0 always (if we want all
records to be grouped into one) or 1/-1 always (if it works and does not cause
too much of reordering) based on what works. Using WritableComparator together
with implementing WritableComparable is slightly more overhead.
> Use VertexGroup and Alias vertex for union
> ------------------------------------------
>
> Key: PIG-3743
> URL: https://issues.apache.org/jira/browse/PIG-3743
> Project: Pig
> Issue Type: Sub-task
> Components: tez
> Reporter: Rohini Palaniswamy
> Assignee: Cheolsoo Park
> Fix For: tez-branch
>
> Attachments: PIG-3743-1.patch, PIG-3743-2.patch,
> PIG-3743-fix-skew.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
