[infinispan-issues] [JBoss JIRA] (ISPN-3236) Repeatable Read: Transactions are not isolated when read non-existing keys

[Pedro Ruivo (JIRA)]

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

Pedro Ruivo updated ISPN-3236:
------------------------------

    Labels: isolation  (was: )

    
> Repeatable Read: Transactions are not isolated when read non-existing keys
> --------------------------------------------------------------------------
>
>                 Key: ISPN-3236
>                 URL: https://issues.jboss.org/browse/ISPN-3236
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 5.3.0.CR1
>            Reporter: Pedro Ruivo
>            Assignee: Pedro Ruivo
>              Labels: isolation
>             Fix For: 5.3.0.Final
>
>
> Repeatable read transaction is not isolated when they read a non-existing key.
> tm.begin()
> cache.get(k) //returns null
> //in the meanwhile a transaction writes on k and commits
> cache.get(k) //return the new value. IMO, this is not valid for 
> REPEATABLE_READ isolation level!
> //TODO add a test case for all the write operations (except put map because it does not read the old value)
>  * put() //assert the return value
>  * conditional put //if cache.get(k) returns null the putIfAbsent should never fail. Vice-version if cache.get(k) returns non-null
>  * conditional replace //replace should never fail if used as old value the cache.get(k). And vice-versa
>  * conditional remove //remove should never fail if used as old value the cache.get(k). And vice-versa

--
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