You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2012/11/21 22:23:59 UTC
[jira] [Resolved] (CRUNCH-117) Custom subclasses of Tuple don't
work with the TupleDeepCopier
[ https://issues.apache.org/jira/browse/CRUNCH-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabriel Reid resolved CRUNCH-117.
---------------------------------
Resolution: Fixed
Pushed to master
> Custom subclasses of Tuple don't work with the TupleDeepCopier
> --------------------------------------------------------------
>
> Key: CRUNCH-117
> URL: https://issues.apache.org/jira/browse/CRUNCH-117
> Project: Crunch
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.3.0, 0.4.0
> Reporter: Josh Wills
> Assignee: Josh Wills
> Fix For: 0.5.0
>
> Attachments: CRUNCH-117b.patch, CRUNCH-117.patch
>
>
> We have the option of serializing custom classes that implement the Tuple interface using the following method on PTypeFamily:
> PType<T> tuples(Class<T>, ...)
> These classes act somewhat like case classes in Scala, and can be used to give useful semantics to something that would otherwise be a Tuple4<Integer, String, Double, Integer> (or some such thing.) Right now, we have a bug in which the static TupleFactory.getTupleFactory does not recognize these custom classes, and so they can't be used in a nested fashion with the deep copier.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira