[
https://issues.apache.org/jira/browse/PIG-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971353#action_12971353
]
Scott Carey commented on PIG-1755:
----------------------------------
{quote}any ideas on how to reduce object allocations?{quote}
Mutable numeric data types. But since the object types are part of the API
that would break things.
Avoiding boxing when doing calculations, but that would be messy and breaks
APIs.
A radical change to Tuple -- changing it to be a reflected object and not
essentially an Object[], would reap huge performance wins but be a very large
effort with API incompatibilities. Maybe Avro will have an API later that
would make such a change simpler, but that is a year or more out.
> Clean up duplicated code in Physical Operators
> ----------------------------------------------
>
> Key: PIG-1755
> URL: https://issues.apache.org/jira/browse/PIG-1755
> Project: Pig
> Issue Type: Improvement
> Reporter: Dmitriy V. Ryaboy
> Assignee: Dmitriy V. Ryaboy
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: PIG-1755.2.patch, PIG-1755.patch
>
>
> A lot of the getNext() implementations in PhysicalOperators is copy-pasted,
> with only the method signatures and casts changing.
> Shorter code leads to less bugs and is easier to read.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
