[
https://jira.jboss.org/browse/ISPN-359?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani updated ISPN-359:
-------------------------------
Fix Version/s: 5.0.0.BETA1
5.0.0.Final
(was: 4.1.0.CR1)
(was: 4.1.0.Final)
Needs more thought and a decision on scoping behaviour
Provide mechanism for users to control data locality when using DIST
--------------------------------------------------------------------
Key: ISPN-359
URL:
https://jira.jboss.org/browse/ISPN-359
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 4.0.0.Final
Reporter: Tero Heinonen
Assignee: Manik Surtani
Fix For: 5.0.0.BETA1, 5.0.0.Final
Programmable affinity either through:
1) statically (e.g. annotating a certain field as the key for consistent hashing)
- in our case this cannot be based on the hashCode() as the affinity requirement and
object identity are not directly related
2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function)
This would help to assign entities (in multiple Caches), which are needed together in the
same nodes (to avoid remote lookups)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira