You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mahout.apache.org by "Sebastian Schelter (JIRA)" <ji...@apache.org> on 2012/08/14 12:42:37 UTC

[jira] [Updated] (MAHOUT-1058) IDRescorers should also be able to filter candidate items

     [ https://issues.apache.org/jira/browse/MAHOUT-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebastian Schelter updated MAHOUT-1058:
---------------------------------------

    Summary: IDRescorers should also be able to filter candidate items  (was: IDRescorers should also be able to filter candidaten items)
    
> IDRescorers should also be able to filter candidate items
> ---------------------------------------------------------
>
>                 Key: MAHOUT-1058
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-1058
>             Project: Mahout
>          Issue Type: New Feature
>          Components: Collaborative Filtering
>    Affects Versions: 0.8
>            Reporter: Sebastian Schelter
>            Assignee: Sebastian Schelter
>
> Currently when a recommendation for a particular user is computed, at first the candidate items are determined via a CandidateItemsStrategy, then predicitions for all these items are computed and afterwards the IDRescorer can filter the items that might be recommended.
> For performance reasons, it should also be possible to apply custom filtering before the estimation is done. This cannot be done in the CandidateItemsStrategy, as the filtering logic might depend on some request/or user-specific criteria that are not known in the recommender application.
> It would be possible to implement such a logic in IDRescorer.isFiltered(), this is however bad for performance reasons, as the very costly estimation has already happen then.
> I propose to add a method to IDRescorer that can filter the candidate items right before estimation starts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira