[
https://issues.apache.org/jira/browse/MAHOUT-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037295#comment-13037295
]
Sean Owen commented on MAHOUT-537:
----------------------------------
I could, though honestly, I think the better solution at this point is to move
to Hadoop 0.21 as part of the next release. It is the current release and
nearly superseded by 0.22. It has some features we need to move forward. It is
closer to what many are using in CDH3/4. The only drawback I see is that Amazon
EMR is on 0.20.2. However we're releasing 0.5 now for 0.20.2. And it is 6
months until we would put out a release needing 0.21, after which time I
imagine 0.22 is out and EMR makes available 0.21 -- or if it doesn't, we have
to leave behind support.
So let me open an item for that, and I suggest you can proceed using 0.21
features here.
(That is what I am doing for personal projects and it really simplified things.
I'm on 0.22 now myself.)
> 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
