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] Updated: (HADOOP-120) Reading an ArrayWriter does not work because valueClass does not get initialized
Date Fri, 11 May 2007 18:47:15 GMT

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

Doug Cutting updated HADOOP-120:
--------------------------------

    Status: Open  (was: Patch Available)

This patch no longer applies to trunk.  It's also not formatted according to Hadoop's conventions.
 Finally, this is not an acceptable approach.  Rather, one could use the workaround suggested
by Owen, or we could add a new Writable class that writes the name of the class in each instance,
but it would not be back-compatible to make this change to ArrayWritable.

> 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.12.3
>         Environment: Red Hat  
>            Reporter: Dick King
>         Assigned To: Owen O'Malley
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message