hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-120) Reading an ArrayWriter does not work because valueClass does not get initialized
Date Wed, 05 Apr 2006 18:25:48 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-120?page=comments#action_12373408 ] 

Andrzej Bialecki  commented on HADOOP-120:
------------------------------------------

Dictionary is stored together inside the file, so I don't think it's a problem - you can always
read it later and restore the data.

Caller may be unaware of exact types stored in a Map-like structure, but it should not prevent
him from knowing (and using) portions of data that he knows about, so I think this doesn't
violate the convention... ok, maybe bends it a little ;)

> Reading an ArrayWriter does not work because valueClass does not get initialized
> --------------------------------------------------------------------------------
>
>          Key: HADOOP-120
>          URL: http://issues.apache.org/jira/browse/HADOOP-120
>      Project: Hadoop
>         Type: Bug

>   Components: io
>  Environment: Red Hat  
>     Reporter: Dick King
>  Attachments: hadoop-120-fix.patch
>
> If you have a Reducer whose value type is an ArrayWriter it gets enstreamed alright but
at reconstruction type when ArrayWriter::readFields(DataInput in) runs on a DataInput that
has a nonempty ArrayWriter , newInstance fails trying to instantiate the null class.

-- 
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


Mime
View raw message