[
https://issues.apache.org/jira/browse/MAHOUT-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044018#comment-13044018
]
Sean Owen commented on MAHOUT-537:
----------------------------------
The people have spoken! Forget 0.21. At best I think we will wait and see on
0.22.
I think the much larger concern in my mind is being as consistent as possible
across the project in how implementations are approached. Within 0.20.x we can
stand to be more consistent -- ideally, not using the deprecated APIs, but
using them if there's a very good reason.
The clustering code is still needlessly different for example, and is going to
be deprecated as a result.
So I think the outcome from this issue is... try to make it as like to the
other M/R jobs in the project? Most everything tries to use the imperfect
AbstractJob thing, which is a good rallying point. I am not sure how realistic
it is here but it would be great to standardize more.
> Bring DistributedRowMatrix into compliance with Hadoop 0.20.2
> -------------------------------------------------------------
>
> Key: MAHOUT-537
> URL: https://issues.apache.org/jira/browse/MAHOUT-537
> Project: Mahout
> Issue Type: Improvement
> Components: Math
> Affects Versions: 0.4, 0.5
> Reporter: Shannon Quinn
> Assignee: Shannon Quinn
> Fix For: 0.6
>
> Attachments: MAHOUT-537.patch, MAHOUT-537.patch, MAHOUT-537.patch,
> MAHOUT-537.patch
>
>
> Convert the current DistributedRowMatrix to use the newer Hadoop 0.20.2 API,
> in particular eliminate dependence on the deprecated JobConf, using instead
> the separate Job and Configuration objects.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
