[infinispan-issues] [JBoss JIRA] Updated: (ISPN-619) Aggregate changes from multiple transactions in AsyncStore

Sanne Grinovero (JIRA) jira-events at lists.jboss.org
Tue Aug 31 18:17:11 EDT 2010


     [ https://jira.jboss.org/browse/ISPN-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sanne Grinovero updated ISPN-619:
---------------------------------

         Assignee: Sanne Grinovero  (was: Manik Surtani)
    Fix Version/s: 4.1.0.Final
                       (was: 5.0.0.BETA1)
      Description: 
After debugging ISPN-618 we found out that the different changes of different transactions are not being coalesced in a smaller set of changes in the AsyncStore (see mailing list).
The AsyncStore implementation should aggregate changes in a "transactions" variable in the same way as AbstractCacheStore, so to push only committed Modifications to the state-changes which are going to be async-applied to the delegated store.

So it seems to make sense to have AbstractDelegatingStore extend the AbstractCacheStore to inherit the same prepare/commit/rollback methods, but this affects all implementations of AbstractDelegatingStore.

  was:
After debugging ISPN-618 we found out that the different changes of different transactions are not being coalesced in a smaller set of changes in the AsyncStore (see mailing list); we choose to solve ISPN-618 just fixing that bug, postponing the optimization idea as it would need more testing while ISPN-618 was found during CR3 testing.
The AsyncStore implementation should aggregate changes in a "transactions" variable in the same way as AbstractCacheStore, so to push only committed Modifications to the state-changes which are going to be async-applied to the delegated store.

So it seems to make sense to have AbstractDelegatingStore extend the AbstractCacheStore to inherit the same prepare/commit/rollback methods, but this affects all implementations of AbstractDelegatingStore.



> Aggregate changes from multiple transactions in AsyncStore
> ----------------------------------------------------------
>
>                 Key: ISPN-619
>                 URL: https://jira.jboss.org/browse/ISPN-619
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Loaders and Stores
>            Reporter: Sanne Grinovero
>            Assignee: Sanne Grinovero
>             Fix For: 4.1.0.Final
>
>
> After debugging ISPN-618 we found out that the different changes of different transactions are not being coalesced in a smaller set of changes in the AsyncStore (see mailing list).
> The AsyncStore implementation should aggregate changes in a "transactions" variable in the same way as AbstractCacheStore, so to push only committed Modifications to the state-changes which are going to be async-applied to the delegated store.
> So it seems to make sense to have AbstractDelegatingStore extend the AbstractCacheStore to inherit the same prepare/commit/rollback methods, but this affects all implementations of AbstractDelegatingStore.

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

        


More information about the infinispan-issues mailing list