[
https://issues.apache.org/jira/browse/PIG-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882597#comment-13882597
]
Rohini Palaniswamy commented on PIG-3719:
-----------------------------------------
Had to create a new instance for the current as moving to the next record in
Tez, resets fields on the current instead of creating a new object. Can you
make it cleaner by making PigNullableWritable implement Cloneable and remove
the newInstance() method in favor of clone(). NullablePartitionWritable can
then override the clone. I should have done that in the first place.
> Fix skewed join e2e tests
> -------------------------
>
> Key: PIG-3719
> URL: https://issues.apache.org/jira/browse/PIG-3719
> Project: Pig
> Issue Type: Sub-task
> Components: tez
> Affects Versions: tez-branch
> Reporter: Cheolsoo Park
> Assignee: Cheolsoo Park
> Fix For: tez-branch
>
> Attachments: PIG-3719-1.patch, PIG-3719-2.patch, PIG-3719-3.patch
>
>
> There are two sets of skewed join e2e tests-
> # tez.conf: Join7 and 8
> # nightly.conf: SkewedJoin
> We need to get both passing.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)