[
https://issues.apache.org/jira/browse/PIG-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olga Natkovich resolved PIG-406.
--------------------------------
Resolution: Fixed
We no longer use IndexedTuple
> The implementation of IndexedTuple might break in cases where a custom
> TupleFactory is being used
> -------------------------------------------------------------------------------------------------
>
> Key: PIG-406
> URL: https://issues.apache.org/jira/browse/PIG-406
> Project: Pig
> Issue Type: Bug
> Components: data
> Affects Versions: 0.2.0
> Reporter: Shubham Chopra
>
> IndexedTuple extends the DefaultTuple. This implementation might break in
> case we are trying to use a custom TupleFactory. Any special data in the
> custom tuples might get lost when we convert it to an IndexedTuple. The
> constructor does a super(t.getAll()), other non-datum attributes will be lost
> after this conversion. The indexedTuple must instead have Tuple as an
> attribute and implement the Tuple interface and delegate all the methods. The
> implementation should be by composition.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
