[
https://issues.apache.org/jira/browse/HADOOP-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602223#action_12602223
]
Tom White commented on HADOOP-3413:
-----------------------------------
Owen,
I agree. This is a problem for the RecordReader interface, which will need work
to change. However, I wasn't proposing we make such a radical change in this
Jira, instead we are making it possible to use the serialization framework with
SequenceFile.Reader, and removing unnecessary dependencies on Writable in some
of the MapReduce layers (so you could at least use Thrift there). Note that the
changes to SequenceFile.Reader are compatible with Java serialization, since
instead of adding
{code}
public boolean next(Object key, Object val)
{code}
there's
{code}
public Object next(Object key)
{code}
and
{code}
public Object getCurrentValue(Object val)
{code}
> SequenceFile.Reader doesn't use the Serialization framework
> -----------------------------------------------------------
>
> Key: HADOOP-3413
> URL: https://issues.apache.org/jira/browse/HADOOP-3413
> Project: Hadoop Core
> Issue Type: Bug
> Components: io
> Affects Versions: 0.17.0
> Reporter: Arun C Murthy
> Assignee: Tom White
> Priority: Critical
> Fix For: 0.18.0
>
> Attachments: hadoop-3413-v2.patch, hadoop-3413-v3.patch,
> hadoop-3413.patch
>
>
> Currently SequenceFile.Reader only works with Writables, since it doesn't use
> the new Serialization framework. This is a glaring considering that
> SequenceFile.Writer uses the Serializer and handles arbitrary types via the
> SerializationFactory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
