[
https://issues.apache.org/jira/browse/MAHOUT-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Eastman updated MAHOUT-294:
--------------------------------
Component/s: Clustering
Sigh. Adding clustering back as an affected component. This is a large issue
across all of Mahout and further refactoring is needed in many areas.
Testability of the command line option processing is complicated by the fact
that run() bundles this in with running the job so the command line stuff
cannot be tested in isolation. This makes testing all of the argument
corner-cases tedious and unnecessarily time-consuming. I'm going to look at
factoring the options parsing out of run.
> Uniform API behavior for Jobs
> -----------------------------
>
> Key: MAHOUT-294
> URL: https://issues.apache.org/jira/browse/MAHOUT-294
> Project: Mahout
> Issue Type: Improvement
> Components: Classification, Clustering, Collaborative Filtering,
> Frequent Itemset/Association Rule Mining, Genetic Algorithms, Math, Utils
> Affects Versions: 0.4
> Reporter: Robin Anil
> Fix For: 0.4
>
> Attachments: MAHOUT-294.patch, MAHOUT-294.patch
>
>
> * Move AbstractJob to common and convert all the Driver classes to extend
> that.
> One suggestion is:
> AlgorithmParams params = ParamsBuilder.build().withParam("-i",
> input).withParam("-o", output)....
> MyAlgorithmn.runJob(params) throws ParameterMissingException;
> * Give uniform command-line parameters for various algorithms.
> e.g Currently distance measure is -d, -dm, -m at different places in
> clustering
> * Add a temp directory as a parameter
> http://www.lucidimagination.com/search/document/28a979aa62c02a1/who_owns_mahout_bucket_on_s3#ddb5855e8bdace45
> This issue will keep track of all discussion/patches related to the design
> and cleanup of Mahout API
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
