[
https://issues.apache.org/jira/browse/HADOOP-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933626#action_12933626
]
Owen O'Malley commented on HADOOP-6685:
---------------------------------------
{quote}
It'd be nicer to have a more specific runtime exception
{quote}
Different types for the exceptions only helps if the user has a reasonable
chance of catching the exception and handling it appropriately. In this case,
there really isn't any useful recovery the user can do.
{quote}
in WritableSerialization.java#getRawComparator, you can use
Class<WritableComparable<Writable>> to avoid the rawtype warning.
{quote}
I don't want to change the signature of WritableComparator.get.
{quote}
I didn't see any tests for Text#readRawString and writeRawString.
{quote}
The should have been moved to the OFile patch. I'll do that for now.
> Change the generic serialization framework API to use serialization-specific
> bytes instead of Map<String,String> for configuration
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-6685
> URL: https://issues.apache.org/jira/browse/HADOOP-6685
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.22.0
>
> Attachments: libthrift.jar, serial.patch, serial4.patch,
> serial6.patch, SerializationAtSummit.pdf
>
>
> Currently, the generic serialization framework uses Map<String,String> for
> the serialization specific configuration. Since this data is really internal
> to the specific serialization, I think we should change it to be an opaque
> binary blob. This will simplify the interface for defining specific
> serializations for different contexts (MAPREDUCE-1462). It will also move us
> toward having serialized objects for Mappers, Reducers, etc (MAPREDUCE-1183).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
