[
https://issues.apache.org/jira/browse/MAHOUT-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240015#comment-13240015
]
tom pierce commented on MAHOUT-994:
-----------------------------------
It would make a lot of sense to me to unify with other Hadoop projects and
start using the hadoop launcher script whenever we can - no need to maintain a
custom reinvented wheel there.
As far as the job jar is concerned, I don't think it's customary to include
Hadoop libs - seems redundant, and potentially dangerous when there are
mismatched versions of classes in the classpath. I know there are ways to
specify/determine which versions of things to use and make this kind of thing
work, but it has been my experience that it always becomes overcomplicated
after a while - it is just bad juju.
Looks like the Hadoop classes in
examples/target/dependency/hadoop-core-0.20.204.0.jar are tacked onto the
classpath inside bin/mahout, which is why standalone mode currently 'just
works' on a box with no hadoop install. This seems less than ideal, though I
can see why it is done.
> mahout script shouldn't rely on HADOOP_HOME since that was deprecated in all
> major Hadoop branches
> --------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-994
> URL: https://issues.apache.org/jira/browse/MAHOUT-994
> Project: Mahout
> Issue Type: Bug
> Components: Integration
> Affects Versions: 0.6
> Reporter: Roman Shaposhnik
>
> Mahout should follow the Pig and Hive example and not rely explicitly on
> HADOOP_HOME and HADOOP_CONF_DIR
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
