[infinispan-issues] [JBoss JIRA] Commented: (ISPN-116) Async cache store should aggregate results for a given key

[Galder Zamarreno (JIRA)]

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

Galder Zamarreno commented on ISPN-116:
---------------------------------------

And also gigaspaces:

- Gigaspaces (http://www.gigaspaces.com/wiki/display/XAP66/Async+Persistency+-+Mirror) cluster-config.groups.group.repl-policy.repl-original-state 	The replication reconciliation mode - This settings should be enabled to ensure that write/take operations or multiple updates of the same entry will be sent to the mirror and not will be discarded when sent within the same batch. 	Default value: false

> Async cache store should aggregate results for a given key
> ----------------------------------------------------------
>
>                 Key: ISPN-116
>                 URL: https://jira.jboss.org/jira/browse/ISPN-116
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Loaders and Stores
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 4.0.0.BETA1
>
>
> Get async cache store to aggregate or coalite multiple changes to a key.
> So, assuming that the modification queue contains 3 changes for key=k1: k1=v1, k1=v2, k1=v3, 
> only write the last one rather than writing all 3 modifications.
> This is something Oracle Coherence already does:
> http://coherence.oracle.com/display/COH34UG/Read-Through%2C+Write-Through%2C+Write-Behind+and+Refresh-Ahead+Caching#Read-Through%2CWrite-Through%2CWrite-BehindandRefresh-AheadCaching-WriteBehindCache

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira