You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Aleksei Udatšnõi (Commented JIRA)" <ji...@apache.org> on 2012/03/01 09:52:04 UTC
[jira] [Commented] (MAHOUT-977) Thread-safe version of
PlusAnonymousUserDataModel with multiple concurrent users
[ https://issues.apache.org/jira/browse/MAHOUT-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219927#comment-13219927 ]
Aleksei Udatšnõi commented on MAHOUT-977:
-----------------------------------------
I just realized that if I to remove the superclass, you'd have to rewrite chapter 5.4 of "Mahout in Action". It references _PlusAnonymousUserDataModel_.
> Thread-safe version of PlusAnonymousUserDataModel with multiple concurrent users
> --------------------------------------------------------------------------------
>
> Key: MAHOUT-977
> URL: https://issues.apache.org/jira/browse/MAHOUT-977
> Project: Mahout
> Issue Type: Improvement
> Components: Collaborative Filtering
> Affects Versions: 0.6
> Reporter: Aleksei Udatšnõi
> Assignee: Sean Owen
> Priority: Minor
> Fix For: 0.7
>
> Attachments: MAHOUT-977.patch
>
>
> This is a suggested improvement to PlusAnonymousUserDataModel.
> Currently the ID of the anonymous user is fixed to Long.MIN_VALUE. Only one set
> of temp data can be inserted into the model and used at one time.
> I propose the change to enable multiple users to insert into this
> model concurrently in a thread-safe manner.
> The idea is to define a pool of available anonymous user IDs. Every
> time a new anonymous user makes a request, the next available
> TEMP_USER_ID is pulled from the queue. After recommendations are
> retrieved, the TEMP_USER_ID can be returned to the pool.
> The discussion about this topic can be found in:
> http://mail-archives.apache.org/mod_mbox/mahout-dev/201202.mbox/%3CCAEccTywC7QJuAJj-u3C1C=WW0yEeBcScUE6Kmj=bedBrxOpsSg@mail.gmail.com%3E
--
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