[
https://issues.apache.org/jira/browse/HADOOP-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536334
]
Tom White commented on HADOOP-1986:
-----------------------------------
>> Except there might not be enough type information to construct an object.
> The factory can keep that around.
Good idea. This is a very neat solution I think.
> Back to my previous comment: with a stateful serializer, is it permitted to
> intersperse other i/o on the stream that's passed to the serializer, or must
> the serializer's
> input or output be reset each time this is done?
I think it is permitted to intersperse - in other words the serializer is not
allowed to buffer the stream.
> Add support for a general serialization mechanism for Map Reduce
> ----------------------------------------------------------------
>
> Key: HADOOP-1986
> URL: https://issues.apache.org/jira/browse/HADOOP-1986
> Project: Hadoop
> Issue Type: New Feature
> Components: mapred
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.16.0
>
> Attachments: SerializableWritable.java, serializer-v1.patch
>
>
> Currently Map Reduce programs have to use WritableComparable-Writable
> key-value pairs. While it's possible to write Writable wrappers for other
> serialization frameworks (such as Thrift), this is not very convenient: it
> would be nicer to be able to use arbitrary types directly, without explicit
> wrapping and unwrapping.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
