[
https://issues.apache.org/jira/browse/MAHOUT-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040656#comment-13040656
]
Elmer Garduno commented on MAHOUT-680:
--------------------------------------
Frank, I was able to run the example tasks without any problems with the
original scripts.
But the problem is still there when I use the scripts with a modified version
of mahout-examples-0.5-job.jar that contains a different analyzer.
Maybe there is a problem with the ClassLoaders, I don't know much about Hadoop
internals, but if I print the CLASSPATH from the mahout script just before
running the task, there are at least two other jars that precede
mahout-examples-0.5-job.jar and contain the
org.apache.mahout.driver.MahoutDriver class.
Any thoughts about this?
> Running the Hadoop script through bin/mahout to set up classpath
> ----------------------------------------------------------------
>
> Key: MAHOUT-680
> URL: https://issues.apache.org/jira/browse/MAHOUT-680
> Project: Mahout
> Issue Type: Improvement
> Affects Versions: 0.4
> Reporter: Frank Scholten
> Priority: Minor
> Fix For: 0.5
>
> Attachments: MAHOUT-680.patch, MAHOUT-680.patch, jobtracker.jsp.html
>
>
> Added a patch which allows you to run the $HADOOP_HOME/bin/hadoop command
> script through the bin/mahout script.
> This way the Mahout script adds the Mahout classes to the $HADOOP_CLASSPATH
> so you can view sequencefiles generated by Mahout jobs with
> bin/mahout hadoop fs -text <sequencefile>
> without having to specify Mahout classes manually or getting
> ClassNotFoundExceptions
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
