[
https://issues.apache.org/jira/browse/MAHOUT-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797277#action_12797277
]
Ted Dunning commented on MAHOUT-185:
------------------------------------
Regarding the properties file idea, I have had very good luck with a convention
that I now use pretty ubiquitously. Each application has a default properties
file that is baked into the jar file. This allows slow changes subject to
recompilation. All of these default properties are subject to over-ride in an
external property file found in the class path or the current working
directory. These over-rides are monitored for changes to allow on-the-fly
reconfiguration of long-running processes.
For transaction systems (not Mahout-like stuff), I also allow requests to
contain an additional over-ride map of properties. This allows certain things
to be changed on a request by request basis. This helps enormously because it
allows almost anything to be the subject of A/B testing.
> Add mahout shell script for easy launching of various algorithms
> ----------------------------------------------------------------
>
> Key: MAHOUT-185
> URL: https://issues.apache.org/jira/browse/MAHOUT-185
> Project: Mahout
> Issue Type: New Feature
> Affects Versions: 0.2
> Environment: linux, bash
> Reporter: Robin Anil
> Fix For: 0.3
>
>
> Currently, Each algorithm has a different point of entry. At its too
> complicated to understand and launch each one. A mahout shell script needs
> to be made in the bin directory which does something like the following
> mahout classify -algorithm bayes [OPTIONS]
> mahout cluster -algorithm canopy [OPTIONS]
> mahout fpm -algorithm pfpgrowth [OPTIONS]
> mahout taste -algorithm slopeone [OPTIONS]
> mahout misc -algorithm createVectorsFromText [OPTIONS]
> mahout examples WikipediaExample
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
