[
https://issues.apache.org/jira/browse/HADOOP-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599450#action_12599450
]
Enis Soztutar commented on HADOOP-3380:
---------------------------------------
I thought that an object of Serialization class captures the semantics of a
Serialization abstraction(such as writable). What I mean is that :
serializationFactory.getSerialization(IntWritable) equals
serializationFactory.getSerialization(DoubleWritable)
In that case, we need to pass the class object to getComparator().
Anyway, aside from this, what is the benefit of tying getComparator() to
serialization instead of a stand alone DefaultComparator#get(ClassName) method
(as in the attached patch)?
> 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
> Attachments: comparator_wip1.patch, comparator_wip1.patch
>
>
> 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.
