[
https://issues.apache.org/jira/browse/HADOOP-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538614
]
Doug Cutting commented on HADOOP-1986:
--------------------------------------
> a serializer than can deserialize more than one class (for example, one for
> Record I/O that can deserialize any class that inherits from the base Record
> I/O class) requires that the classes all be constructed the same way
Yes, that's more-or-less assumed, but I yet fail to see it as a problem. All
record classes are generated from an IDL and it should be easy to generate a
no-arg ctor for those. Ditto for thrift. Things that implement Writable today
already must have a no-arg ctor. Can you please provide a more detailed
example of something that would prove difficult and why it is important that it
be easy?
> 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.
