hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cameron Pope (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (HADOOP-120) Reading an ArrayWriter does not work because valueClass does not get initialized
Date Thu, 13 Sep 2007 20:27:32 GMT

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

camerooni edited comment on HADOOP-120 at 9/13/07 1:27 PM:
--------------------------------------------------------------

Yes, that's definitely a better fix and if anyone is using ArrayWritable's default constructor,
it should be easy to change.

      was (Author: camerooni):
    Yes, that's definitely a better fix and if anyone is using ArrayWritable's default constructor,
it sould be easy to change.
  
> Reading an ArrayWriter does not work because valueClass does not get initialized
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-120
>                 URL: https://issues.apache.org/jira/browse/HADOOP-120
>             Project: Hadoop
>          Issue Type: Bug
>          Components: io
>    Affects Versions: 0.15.0
>         Environment: Red Hat  
>            Reporter: Dick King
>            Assignee: Doug Cutting
>         Attachments: HADOOP-120-3.patch, hadoop-120-fix.patch, hadoop-120-workaround.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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message