[
https://issues.apache.org/jira/browse/MAHOUT-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429122#comment-13429122
]
Sean Owen commented on MAHOUT-1050:
-----------------------------------
In my view the only essential condition is avoiding corrupting data structures
or exceptions due to concurrent modification. It is OK for a request to see an
update partly completed, or a reload not yet finished, I think. Reads should be
able to proceed concurrently, so some kind of ReadWriteLock is probably needed.
Beyond that, overly coarse synchronization (i.e. one lock for the whole class)
feels OK to me.
> mutable in-memory datamodel
> ---------------------------
>
> Key: MAHOUT-1050
> URL: https://issues.apache.org/jira/browse/MAHOUT-1050
> Project: Mahout
> Issue Type: Improvement
> Components: Collaborative Filtering
> Affects Versions: 0.7
> Environment: independant
> Reporter: Renaud Richardet
> Assignee: Sean Owen
> Priority: Minor
> Fix For: 0.7
>
> Attachments: MutableDataModel.java
>
>
> I could not find an in-memory DataModel that supports setPreference /
> removePreference / refresh. Instead, they all "recreate" a new
> GenericDataModel anytime one adds or remove preferences.
--
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
