[
https://issues.apache.org/jira/browse/HADOOP-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598204#action_12598204
]
Owen O'Malley commented on HADOOP-3380:
---------------------------------------
Enis,
I think the fact that the raw comparators depend on the serialization used
is precisely why Doug wants to put it there. It seemed wrong to me at first,
but it is growing on me. One very unfortunate part of using raw comparators is
that Hadoop doesn't have a reasonable story if the user wants to do
object-based compares. (Ignoring the utterly non-performant raw comparator that
deserializes the two keys and calls compare on them.)
> need comparators in serializer framework
> ----------------------------------------
>
> Key: HADOOP-3380
> URL: https://issues.apache.org/jira/browse/HADOOP-3380
> Project: Hadoop Core
> Issue Type: New Feature
> Components: io
> Reporter: Doug Cutting
>
> The new serialization framework permits Hadoop to incorporate different
> serialization systems, including Hadoop's Writable, Thrift, Java
> Serialization, etc. It provides a generic, extensible means
> (SerializationFactory) to create serializers and deserializers for arbitrary
> Java classes. However it does not include a generic means to create
> comparators for these classes. Comparators are required for MapReduce keys
> and many other computations. Thus we should enhance the serialization
> framwork to provide comparators too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
