[jira] [Resolved] (MAHOUT-1864) Twenty Newsgroups Classification Example fails in case running with MAHOUT_LOCAL=true

["Andrew Palumbo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAHOUT-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Palumbo resolved MAHOUT-1864.
------------------------------------
    Resolution: Won't Fix
      Assignee: Andrew Palumbo

Agreed

> Twenty Newsgroups Classification Example fails in case running with MAHOUT_LOCAL=true 
> --------------------------------------------------------------------------------------
>
>                 Key: MAHOUT-1864
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-1864
>             Project: Mahout
>          Issue Type: Improvement
>          Components: Examples
>    Affects Versions: 0.12.0
>            Reporter: giriraj sharma
>            Assignee: Andrew Palumbo
>            Priority: Minor
>              Labels: easyfix, easytest, newbie
>             Fix For: 0.13.0
>
>
> Twenty Newsgroups Classification Example fails in case running with {{MAHOUT_LOCAL=true}} or else when {{HADOOP_HOME}} env variable is not set.
> [Newsgroups|https://mahout.apache.org/users/classification/twenty-newsgroups.html] lists instructions in order to run this classifier. When running in standalone mode({{MAHOUT_LOCAL=true}}), i.e., running {{$ ./examples/bin/classify-20newsgroups.sh}}, the script runs {{./examples/bin/set-dfs-commands.sh}} internally to export hadoop related env variables.
> {{set-dfs-commands.sh}} attempts to check for hadoop version despite running with {{MAHOUT_LOCAL}} set as true. IMHO, the script works fine considering the prerequisites, but, it will as well make sense if we can update the script {{./examples/bin/set-dfs-commands.sh}} to export hadoop env varibales only in case {{MAHOUT_LOCAL}} is not set to true.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)