[
https://issues.apache.org/jira/browse/MAHOUT-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852477#action_12852477
]
Jake Mannix commented on MAHOUT-350:
------------------------------------
bq. I suppose I hadn't wanted to be presumptuous and do that without some
support, but sounds like this has some consensus.
Yep, I've been subclassing AbstractJob all over in the decomposer /
DistributedRowMatrix stuff already.
I've had some odd issues with pseudo-distributed vs. really distributed usage
and command line options parsing with *optional* options with it though. I'll
try to post the exact problem, but I think I'm not properly using the mixture
of commons.cli2 together with the GenericOptionsParser when I subclass
AbstractJob though...
> 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.
