[jira] Commented: (MAHOUT-143) Refactor Hadoop deprecations

["Sean Owen (JIRA)" <ji...@apache.org>]

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

Sean Owen commented on MAHOUT-143:
----------------------------------

Here are the facts I've gathered after a lot of experimentation:

0.22 is way too bleeding edge -- our code doesn't even compile against it.
0.21 compiles, but the docs and tools aren't quite in place. With some hacking, I got the cluster partly up but not completely, and am already far enough in to feel this is also too bleeding edge.
0.20 runs our code that's written for old 0.19 APIs. It runs some of the code written for 0.20 APIs but not all -- has bugs only fixed in 0.21
0.19 works of course, but isn't the latest release and its APIs are deprecated
0.18 is what stuff like Amazon Elastic Mapreduce runs

So, I can't make progress on 0.20. I can make progress on 0.21 I imagine, but when it comes out. 
I can move back to use 0.19 APIs (which hopefully work on 0.18 too). It will work on 0.20. That would at least put us on one consistent version of Hadoop, and back in a working state.

I suggest we do not move to new APIs en masse until 0.21 is released and stabilizes.

> Refactor Hadoop deprecations
> ----------------------------
>
>                 Key: MAHOUT-143
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-143
>             Project: Mahout
>          Issue Type: Improvement
>    Affects Versions: 0.2
>            Reporter: Grant Ingersoll
>            Assignee: Sean Owen
>            Priority: Minor
>             Fix For: 0.3
>
>
> Hadoop 0.20.0 deprecates JobConf in favor of a Configuration.  Need to investigate what this means and convert to using it.  Seems to now require some XML based approach.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.