hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dick King (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 15:32:43 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-120?page=comments#action_12373388 ] 

Dick King commented on HADOOP-120:
----------------------------------

Regarding the dictionary approach ... remember the life of a dictionary is the lifetime of
a DFS, not merely a particular run or a DFS file.  Also it does violate the apparent convention
that the callER knows the type of the object.  Now maybe that should be rethought, but we
should do so explicitly, not back into it.

-dk


> 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