[infinispan-issues] [JBoss JIRA] Commented: (ISPN-312) Ability to group data entries
[
https://issues.jboss.org/browse/ISPN-312?page=com.atlassian.jira.plugin.s...
]
Erik Salter commented on ISPN-312:
----------------------------------
Here's what I mean.
{code}
Group class InternalResourceKey {
String group;
...
@Group
String getGroup() {
return group;
}
}
{code}
{code}
InternalResourceKey key = new InternalResourceKey();
...
resourceCache.lock( key );
// Get the previous result.
ResourceResult result = resourceCache.get( key );
ResourceResult newResult = doWork( key, result );
resourceCache.put( key, newResult );
// I also want to group an external identifier that an external client knows about with
the result so they will be on the same node
employeeCache.put( "111-111-1111", newResult, key.getGroup() );
{code}
Ability to group data entries
-----------------------------
Key: ISPN-312
URL: https://issues.jboss.org/browse/ISPN-312
Project: Infinispan
Issue Type: Feature Request
Components: Core API, Distributed Cache, Eviction, Locking and Concurrency
Affects Versions: 4.0.0.Final, 4.1.0.Final
Reporter: Mindaugas Žakšauskas
Assignee: Pete Muir
Priority: Minor
Labels: cache, colocation, group, grouping
Fix For: 5.1.0.BETA1
This is a spin-off from
http://lists.jboss.org/pipermail/infinispan-dev/2009-December/001968.html.
The requested feature would allow distinct entries to be assigned to custom arbitrary
groups. Later in time those groups could be flushed on demand without any knowledge of
entry keys.
This feature exists in other open source cache library, see:
http://www.opensymphony.com/oscache/api/com/opensymphony/oscache/base/Cac...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira