[
https://issues.apache.org/jira/browse/MAHOUT-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852224#action_12852224
]
Drew Farris commented on MAHOUT-350:
------------------------------------
{quote}
Hmm, I don't understand that. AbstractJob.class and ItemIDIndexMapper.class are
in the same .jar file. There is only one .jar, with both, so both ought to end
up selecting the same .jar file. I'd rather specify the Mapper class instead
just because maybe someday someone subclasses AbstractJob, puts the
implementation in a different jar, and then this line won't work.
{quote}
How about jobConf.setJarByClass(getClass()) in AbstractJob's prepareJobConf?
This will always set the jar based on the AbstractJob implementation being
executed.
{quote}
I was looking to see how Hadoop accepts arguments like "-Dmapred...." on the
command line. I can't find it parsing these anywhere. So I don't know this
exists.
{quote}
ToolRunner.run(..) runs the args through GenericOptionsParser, which adds the
results to the conf, which then gets set back on the object being run that
implements the Configured interface. These are pulled in by AbstractJob when it
creates the jobConf using the getConf() argument.
{quote}
AbstractJob has four sub-job ,they displayed the same name, It hard to know
which phase does the job run in .
{quote}
In this vein, it would be handy if AbstractJob's prepareJobConf method could
take a string argument for the subjob name and allow the name to be specified
by the class calling it -- requiring that the name only be specified on the
command-line forces all jobs run under the umbrella of the command to have the
same name. Maybe take any current value of mapred.job.name (if specified) and
append the string to it?
> 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.
