[
https://issues.apache.org/jira/browse/HADOOP-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536201
]
Tom White commented on HADOOP-1986:
-----------------------------------
Vivek,
I was thinking of the first way.
> Frameworks that expect the caller to create an object before deserializing it
> (Thrift, Record I/O), would return NULL,
> but others that create their own objects would accept a NULL value for the
> 'reuse' parameter.
It's a small point but I think the return value would always be non-null for
convenience. The contract would be that the deserialize method always returns a
deserialized object. Deserializers for Thrift, Record I/O etc. would just
return the "reuse" object.
> 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.
