[ 
https://issues.apache.org/jira/browse/MAHOUT-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721896#comment-13721896
 ] 

Maysam Yabandeh commented on MAHOUT-1284:
-----------------------------------------

The error that you get (and I do not manage to reproduce) does seem to be 
related to the patch. It complains that #getValue method does not exist, which 
is not affected by the patch.
{code}
java.lang.NoSuchMethodError: 
org.apache.mahout.common.DummyRecordWriter.getValue(Ljava/lang/Object;)Ljava/util/List;
        at 
org.apache.mahout.utils.TestConcatenateVectorsJob.testConcatenateVectorsReducer(TestConcatenateVectorsJob.java:90)
{code}
Is there any chance that your test file is not compiled properly. It seems that 
your TestConcatenateVectorsJob.class is compiled against the old 
DummyRecordWriter.class.

I regenerated the second patch against the latest trunk just to ensure that 
there is no behind-the-trunk issue here, and you are right that it still did 
not change the patch.
                
> DummyRecordWriter's bug with reused Writables
> ---------------------------------------------
>
>                 Key: MAHOUT-1284
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-1284
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.7, 0.8
>            Reporter: Maysam Yabandeh
>            Assignee: Suneel Marthi
>            Priority: Minor
>              Labels: test
>             Fix For: 0.9
>
>         Attachments: MAHOUT-1284.patch, MAHOUT-1284.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> It is a recommended practice to reuse the Writable objects. 
> DummyRecordWriter, which is used for testing in Mahout, however keeps the 
> same Writable instance in a map: next time that the user reuses the Writable 
> object, the internal map of DummyRecordWriter changes as well. This makes 
> DummyRecordWriter fail for testing the MapReduce jobs that reuse the 
> Writables.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to