[infinispan-issues] [JBoss JIRA] (ISPN-1616) Provide removeAll bulk operation on Cache
Manik Surtani (Updated) (JIRA)
jira-events at lists.jboss.org
Wed Dec 14 16:07:09 EST 2011
[ https://issues.jboss.org/browse/ISPN-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manik Surtani updated ISPN-1616:
--------------------------------
Fix Version/s: 6.0.0.FINAL
It only reduces the number of RPCs if you have a pessimistically locked cache. Not otherwise.
> Provide removeAll bulk operation on Cache
> -----------------------------------------
>
> Key: ISPN-1616
> URL: https://issues.jboss.org/browse/ISPN-1616
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core API, RPC
> Affects Versions: 5.1.0.CR1
> Reporter: Mathieu Lachance
> Assignee: Manik Surtani
> Priority: Minor
> Fix For: 6.0.0.FINAL
>
>
> is there any reason why api do not provide remove all operation, while there's lock(K...) putAll(Map<K,V>) operations ?
> it would be great to add remove all capabilities to org.infinispan.Cache.
> i guess it could also reduce the numbers of rpc calls in the following situation :
> cache.getAdvancedCache().getTransactionManager().begin();
> cache.lock("a", "b", "c");
> cache.remove("a");
> cache.remove("b");
> cache.remove("c");
> cache.getAdvancedCache().getTransactionManager().commit();
> which could be re-implemented this way :
> cache.getAdvancedCache().getTransactionManager().begin();
> cache.lock("a", "b", "c");
> cache.remove("a", "b", "c");
> cache.getAdvancedCache().getTransactionManager().commit();
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list