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

Sean Owen updated MAHOUT-708:
-----------------------------

          Description: 
I suggest we should move to Hadoop 0.20.203.0 for the next release. (Not 0.21 
or further.) It is a much more recent branch of 0.20.x and is compile-time 
compatible with 0.20.2 in our code already.

However I know already that switching to it causes some failures, in the 
Lanczos jobs for instances. Looks like something's expecting a file somewhere 
that isn't where it used to be. I bet it's an easy fix, but don't know what it 
is yet.

  was:
I suggest we should move to Hadoop 0.21 for the next release. It is the current 
release, soon to be superseded by 0.22. It matches more closely what CDH3/4 
users use. It has bug fixes, and crucially some features that make joins much 
less painful.

The drawback is that EMR does not yet support it. I still suggest we forge 
ahead as one imagines it will be supported by the time we release 0.6.

    Affects Version/s:     (was: 0.6)
        Fix Version/s:     (was: 1.0)
                       0.6
              Summary: Update to Hadoop 0.20.203.0  (was: Update to Hadoop 0.21)

> Update to Hadoop 0.20.203.0
> ---------------------------
>
>                 Key: MAHOUT-708
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-708
>             Project: Mahout
>          Issue Type: Task
>          Components: Classification, Clustering, Collaborative Filtering, 
> Frequent Itemset/Association Rule Mining
>    Affects Versions: 0.5
>            Reporter: Sean Owen
>            Assignee: Sean Owen
>              Labels: hadoop
>             Fix For: 0.6
>
>
> I suggest we should move to Hadoop 0.20.203.0 for the next release. (Not 0.21 
> or further.) It is a much more recent branch of 0.20.x and is compile-time 
> compatible with 0.20.2 in our code already.
> However I know already that switching to it causes some failures, in the 
> Lanczos jobs for instances. Looks like something's expecting a file somewhere 
> that isn't where it used to be. I bet it's an easy fix, but don't know what 
> it is yet.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to