hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-414) replace class UTF8 with class Text
Date Fri, 01 Sep 2006 23:47:25 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-414?page=comments#action_12432258 ] 
Doug Cutting commented on HADOOP-414:

> we would like to move to the new method of writing Strings (Text.writeString), but can't
very easily because even if the file versions and the rpc protocol versions change, that doesn't
get passed down to readFields

I'm not sure what you're saying.  If we, in a single commit, change from UTF8 to Text  in
RPC parameter classes and in classes written to disk, and increase the version numbers of
the file formats and RPC protocols involved, then we'd be safe, no?  The problem is that if
we change from UTF8 to Text in the RPC system, when transmitting class names, since this has
no version.  It would be good to get a version number here.

More generally, it would be useful to have a per-Writable class version number.  This could
be used when setting up RPC connections, and stored in file formats, etc.  But that would
not solve the current problem with the RPC system.

Maybe we should punt on the RPC system for this patch for now, and just make the changes that
are easy, leaving that for another day?

> replace class UTF8 with class Text
> ----------------------------------
>                 Key: HADOOP-414
>                 URL: http://issues.apache.org/jira/browse/HADOOP-414
>             Project: Hadoop
>          Issue Type: Improvement
>    Affects Versions: 0.5.0
>            Reporter: Hairong Kuang
>         Assigned To: Hairong Kuang
>             Fix For: 0.6.0
>         Attachments: utf2text.patch
> Since class UTF8 is deprecated, all references of UTF8 in hadoop should be replaced with
class Text if the change does not break the system. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message