[
https://issues.apache.org/jira/browse/MAHOUT-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Drew Farris reopened MAHOUT-811:
--------------------------------
Assignee: Drew Farris (was: Sean Owen)
This patch introduces another problem, specifically with the following line:
{code}
cd ${WORK_DIR}/reuters-sgm && tar xzf ../reuters21578.tar.gz && cd .. && cd ..
{code}
Here the script is making assumptions as to where the ${WORK_DIR} is located,
and cd-ing relative to that to get to the mahout exampless bin directory in
order to later execute ../../bin/mahout.
As a result, the script will fail any time it needs to download and untar the
reuters data.
One fix would be to make the script a little smarter about where the mahout
driver script is located by taking advantage of ${SCRIPT_PATH}
Also, it would be nice if the work dir could be read from an environment
variable. If the env variable is not set, it could be set to
/tmp/mahout-work-${user}.
> Mahout examples try to write to examples/bin/work, which may not be writeable
> by current user
> ---------------------------------------------------------------------------------------------
>
> Key: MAHOUT-811
> URL: https://issues.apache.org/jira/browse/MAHOUT-811
> Project: Mahout
> Issue Type: Bug
> Components: Examples
> Affects Versions: 0.5
> Reporter: Andrew Bayer
> Assignee: Drew Farris
> Fix For: 0.6
>
> Attachments: MAHOUT-811.diff.txt
>
>
> The examples in examples/bin create subdirectories (either work or
> mahout-work) in that directory and write to those subdirectories. This works
> fine if the current user has write access to examples/bin, but if not (such
> as in the case of the package generated by Bigtop, in which the files are
> installed to /usr/lib/mahout and owned by root), the examples can't run. This
> is causing BIGTOP-96, but needs to be fixed in Mahout. The patch I'm
> attaching changes all the references to work, examples/bin/work, and
> mahout-work to instead use /tmp/mahout-work-${USER}, which will be writeable.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
