hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Radim Kolar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8619) WritableComparator must implement no-arg constructor
Date Tue, 31 Jul 2012 09:48:35 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425639#comment-13425639
] 

Radim Kolar commented on HADOOP-8619:
-------------------------------------

I know how to use Writeable interface. I coded about 110k lines in hadoop of code in last
8 months. Its unusable beyond easy stuff. If Writable is that good, why you are not using
it for serializing communication in YARN. You use avro and protobuf. Isnt one serialization
approach sufficient for usage? It is, but its not effective. Thats why you are not using Writable
everywhere.

But my point is not to discuss if Writable sucks or not. Point is why you are trying on purpose
put obstacles in using other serialization frameworks. You call it "protection" but its some
kind of protection as you can get by communist government. It was proved by history that communist
protection failed, it created sick society where everybody were poor.

Do not try to lock developers into one right thing. Give them freedom.

I do not have infinite time in hand. I could not wait years until you guys decide, maybe we
should commit these 3 lines of code. I need to act now, my project needs it.
                
> WritableComparator must implement no-arg constructor
> ----------------------------------------------------
>
>                 Key: HADOOP-8619
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8619
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: io
>    Affects Versions: 3.0.0
>            Reporter: Radim Kolar
>             Fix For: 0.23.0, 2.0.0-alpha, 3.0.0
>
>         Attachments: writable-comparator.txt
>
>
> Because of reasons listed here: http://findbugs.sourceforge.net/bugDescriptions.html#SE_COMPARATOR_SHOULD_BE_SERIALIZABLE
> comparators should be serializable. To make deserialization work, it is required that
all superclasses have no-arg constructor. http://findbugs.sourceforge.net/bugDescriptions.html#SE_NO_SUITABLE_CONSTRUCTOR
> Simply add no=arg constructor to  WritableComparator.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message