[
https://issues.apache.org/jira/browse/MAHOUT-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037461#comment-13037461
]
Jake Mannix commented on MAHOUT-708:
------------------------------------
I'm open to being convinced, but as stated on the list, I'm starting from a
position of -1 on this.
For the same reason that Lucene didn't move to Java 5 until *last year*, we may
be stuck with mixed 0.18/0.20+ apis for quite some time.
Anyone running their own cluster can certainly upgrade to 0.22, but production
systems, by and large, are far more conservative, and have also often been
bitten by hadoop upgrades (0.19, anyone?) in the past, and so are really loathe
to just jump onto the newest "blessed" release.
If someone can convince me that everyone has moved on to 0.21+, then sure. But
so far, that is not my experience, at all.
> Update to Hadoop 0.21
> ---------------------
>
> 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.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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
