[
https://issues.apache.org/jira/browse/PIG-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941154#comment-13941154
]
Rohini Palaniswamy edited comment on PIG-3789 at 3/19/14 11:19 PM:
-------------------------------------------------------------------
Lets just commit this patch. I will create a separate jira and put up a patch
for the newTupleNoCopy optimization after Mark's POPackage refactor goes into
trunk.
+1
was (Author: rohini):
Lets just commit this patch. I will create a separate jira and put up a patch
for the newTupleNoCopy optimization after Mark's POPackage refactor goes into
trunk.
> tuple in POStream binaryInputQueue keep changing
> ------------------------------------------------
>
> Key: PIG-3789
> URL: https://issues.apache.org/jira/browse/PIG-3789
> Project: Pig
> Issue Type: Sub-task
> Components: tez
> Affects Versions: tez-branch
> Reporter: Daniel Dai
> Assignee: Daniel Dai
> Fix For: tez-branch
>
> Attachments: PIG-3789-1.patch, PIG-3789-2.patch
>
>
> Similar to the comments in POSimpleTezLoad:
> {code}
> /**
> * Previously, we reused the same Result object for all results, but we
> found
> * certain operators (e.g. POStream) save references to the Result object
> and
> * expect it to be constant.
> */
> {code}
> Tuples put into binaryInputQueue get changed when it is actually processed.
> Not exactly sure why, but make a copy of the tuple solves the issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
