mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Goldstein (JIRA)" <j...@apache.org>
Subject [jira] Created: (MAHOUT-426) The Mahout command script doesn't properly run when Hadoop is installed but $MAHOUT_JOB is not set or found in standard locations
Date Wed, 23 Jun 2010 00:00:56 GMT
The Mahout command script doesn't properly run when Hadoop is installed but $MAHOUT_JOB is
not set or found in standard locations
---------------------------------------------------------------------------------------------------------------------------------

                 Key: MAHOUT-426
                 URL: https://issues.apache.org/jira/browse/MAHOUT-426
             Project: Mahout
          Issue Type: Bug
    Affects Versions: 0.4
         Environment: Manifested in Amazon EC2 instance set up according to wiki instructions
- https://cwiki.apache.org/MAHOUT/mahoutec2.html
Seems likely to affect any server where Hadoop is installed
            Reporter: Peter Goldstein


In the case where no $MAHOUT_JOB is set, and no mahout-examples-*.job file is found in the
standard locations, the Mahout command script should default to the run locally option.  Instead,
when the script is run one received an error that the non-existent file "$MAHOUT_HOME/mahout-examples-*.job"
cannot be found.

This is the result of two separate bugs in the Mahout command script:

i) There is no existence check in the loop checking for mahout-examples-*.job files in $MAHOUT_HOME
ii) The execution if/else clause only checks if either $HADOOP_CONF_DIR or $HADOOP_HOME is
empty when determining whether to run locally.  It also should check the $MAHOUT_JOB variable,
as it is meaningless to run hadoop in this case.

Fixing these two issues allowed me to (almost) run the $MAHOUT_HOME/examples/bin/build-reuters.sh
script.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message