[infinispan-issues] [JBoss JIRA] (ISPN-3900) Expose mechanism to retrieve the set of keys associated with a group
Paul Ferraro (JIRA)
issues at jboss.org
Tue Mar 18 17:36:10 EDT 2014
[ https://issues.jboss.org/browse/ISPN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro updated ISPN-3900:
-------------------------------
Description:
The grouping API allows the association of set of keys to a group. It would be useful to be able to obtain the set of keys associated with a given group.
In WildFly, a web session is stored using multiple cache entries, one entry for the session meta data (key is session id), and one entry for each session attribute (key is session id + attribute name). In order to look up find all the entries for a given session, the cache entry storing the meta has to store an additional Set<String> of attribute names so that I can locate all session attribute cache entries for a given session. Not only information redundant and bloats the session, but if I add or remove session attributes, I additionally need to replace the value for the cache entry containing the session meta data (since the set it contains will have mutated). This latter part could be avoided if Infinispan provided a mechanism to return all the cache keys that map to a given group.
was:The grouping API allows the association of set of keys to a group. It would be useful to be able to obtain the set of keys associated with a given group.
> Expose mechanism to retrieve the set of keys associated with a group
> --------------------------------------------------------------------
>
> Key: ISPN-3900
> URL: https://issues.jboss.org/browse/ISPN-3900
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 6.0.1.Final
> Reporter: Paul Ferraro
> Assignee: Mircea Markus
>
> The grouping API allows the association of set of keys to a group. It would be useful to be able to obtain the set of keys associated with a given group.
> In WildFly, a web session is stored using multiple cache entries, one entry for the session meta data (key is session id), and one entry for each session attribute (key is session id + attribute name). In order to look up find all the entries for a given session, the cache entry storing the meta has to store an additional Set<String> of attribute names so that I can locate all session attribute cache entries for a given session. Not only information redundant and bloats the session, but if I add or remove session attributes, I additionally need to replace the value for the cache entry containing the session meta data (since the set it contains will have mutated). This latter part could be avoided if Infinispan provided a mechanism to return all the cache keys that map to a given group.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list