mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paritosh Ranjan (JIRA)" <>
Subject [jira] [Commented] (MAHOUT-1108) executes seqdirectory with MAHOUT_LOCAL=true
Date Thu, 01 Nov 2012 11:21:13 GMT


Paritosh Ranjan commented on MAHOUT-1108:

I tend to agree with you.

I don't see the point of extracting it locally and the putting the files in hdfs. From what
I can see, nothing else is done sequentially (locally) in this script. So, MAHOUT_LOCAL seems
to be redundant to me.

Still, I think that the first mapreduce call be after 

  if [ ! -e $HADOOP ]; then
    echo "Can't find hadoop in $HADOOP, exiting"
    exit 1

so that the user is warned with a proper message.

Since I am not the creator of this script, and I am not sure about the use of MAHOUT_LOCAL,
I would like to wait for someone to clarify the doubts regarding MAHOUT_LOCAL. Then, I think
we can go ahead this change with some modifications ( like putting the mapreduce call after
the check of hadoop's existence).

> executes seqdirectory with MAHOUT_LOCAL=true
> ---------------------------------------------------------------
>                 Key: MAHOUT-1108
>                 URL:
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Elmer Garduno
>            Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> Got the following exception when running the command with HADOOP_CONF and  HADOOP_CONF_DIR
> Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/hadoop/util/ProgramDriver
> 	at org.apache.mahout.driver.MahoutDriver.main(
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.util.ProgramDriver
> 	at$ Source)
> 	at Method)
> 	at Source)
> 	at java.lang.ClassLoader.loadClass(Unknown Source)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
> 	at java.lang.ClassLoader.loadClass(Unknown Source)
> 	... 1 more

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message