[jira] Resolved: (MAHOUT-414) Usability: Mahout applications need a consistent API to allow users to specify desired map/reduce concurrency

["Jeff Eastman (JIRA)" <ji...@apache.org>]

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

Jeff Eastman resolved MAHOUT-414.
---------------------------------

      Assignee: Jeff Eastman
    Resolution: Fixed

All the clustering applications now use AbstractJob which supports the -D arguments for configuring Hadoop. All now call getConf() so that this parameter is handled correctly from the CLI, and numReducers option has been removed. Marking as closed.

> Usability: Mahout applications need a consistent API to allow users to specify desired map/reduce concurrency
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: MAHOUT-414
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-414
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.3
>            Reporter: Jeff Eastman
>            Assignee: Jeff Eastman
>             Fix For: 0.4
>
>
> If specifying the number of mappers and reducers is a common activity which users need to perform in running Mahout applications on Hadoop clusters then we need to have a standard way of specifying them in our APIs without exposing the full set of Hadoop options, especially for our non-power-users. This is the case for some applications already but others require the use of Hadoop-level -D arguments to achieve reasonable out-of-the-box parallelism even when running our examples. The usability defect is that some of our algorithms won't scale without it and that we don't have a standard way to express this in our APIs. 

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