[
https://issues.apache.org/jira/browse/MAHOUT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860284#action_12860284
]
Sean Owen commented on MAHOUT-305:
----------------------------------
What do you mean about the secondary sort and is it something I can set about
porting / writing?
Yes it may be inevitable that one has to prune the data to run this reasonably.
It doesn't necessarily hurt. We probably need better facilities than
hard-coding taking the top 20.
I suggest we merge into the .item implementation, since it resembles the rest
of the code base (both other MR jobs and recommender bits) somewhat more. The
framework of has been kind of debugged by a few users, and now the machinery
has the best of both worlds inside, including a few more new tricks. You're
welcome to continue messing with it.
> Combine both cooccurrence-based CF M/R jobs
> -------------------------------------------
>
> Key: MAHOUT-305
> URL: https://issues.apache.org/jira/browse/MAHOUT-305
> Project: Mahout
> Issue Type: Improvement
> Components: Collaborative Filtering
> Affects Versions: 0.2
> Reporter: Sean Owen
> Assignee: Ankur
> Priority: Minor
>
> We have two different but essentially identical MapReduce jobs to make
> recommendations based on item co-occurrence:
> org.apache.mahout.cf.taste.hadoop.{item,cooccurrence}. They ought to be
> merged. Not sure exactly how to approach that but noting this in JIRA, per
> Ankur.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
