[
https://issues.apache.org/jira/browse/MAHOUT-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852012#action_12852012
]
Drew Farris commented on MAHOUT-350:
------------------------------------
Not sure if this is helpful Sean, GenericOptionsParser should be picking up the
-Dproperty=value arugments -- iirc this handled somewhere in the ToolRunner.
The run method's args would have any args left over after the
GenericOptionsParser had done its thing. As long as the JobConf is created
using the right configuration object, the job should be picking them up. It
looks like AbstractJob should be doing this.
GenericOptionsParser handles a bunch of other handy arguments, the javadoc
covers it. It should work without having to do a bunch of argument parsing. If
you'd like I can take a closer look this evening.
> add one "JobName" and reduceNumber parameter to
> org.apache.mahout.cf.taste.hadoop.item.RecommenderJob
> ------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-350
> URL: https://issues.apache.org/jira/browse/MAHOUT-350
> Project: Mahout
> Issue Type: Improvement
> Components: Collaborative Filtering
> Affects Versions: 0.4
> Reporter: Hui Wen Han
> Priority: Minor
> Attachments: screenshot-1.jpg
>
>
> Can add one "JobName" parameter to
> org.apache.mahout.cf.taste.hadoop.item.RecommenderJob?
> if there's a lot of RecommenderJob,it's hard to distinguish those jobs.
> also RecommenderJob has four sub jobs (or phase ) ,can add sub-job name to
> those phase ?
> Because RecommenderJob has not setNumReduceTasks ,it seems that the
> performance is not good in reduce phase.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
