[infinispan-issues] [JBoss JIRA] (ISPN-1616) Provide removeAll bulk operation on Cache

[Mircea Markus (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960522#comment-12960522 ] 

Mircea Markus commented on ISPN-1616:
-------------------------------------

Just to clarify Manik's last comment, if you're using optimistic tx caches, this optimisation takes place anyway. For pessimistic and non-tx caches it doesn't.
                
> 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
>    Affects Versions: 5.1.0.CR1
>            Reporter: Mathieu Lachance
>            Assignee: Manik Surtani
>            Priority: Minor
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira