vitthalbywar-tibco commented on issue #12540:
URL: https://github.com/apache/ignite/issues/12540#issuecomment-3769012771
Hello @sk0x50 ,
Thank you for the detailed explanation and your response.
So as I understood, the key reason for this inconsistent(?) read during Tx1
commit phase is due to lock is sequentially released on the keys participating
in Tx1 (being read in Tx2) and its not released atomically on all the
participating keys.
Isn't it contradicting with fully ACID compliant transactions
expectations(vs traditional RDBMS)?
Any recommendations for use cases requiring atomic visibility without
REPEATABLE_READ/SERIALIZABLE overhead?
- Was TRANSACTIONAL_SNAPSHOT/MVCC the intended solution? (Now deprecated)
- Are there alternative approaches recommended?
- is there something in later versions of Ignite to support above?
Thank you again for looking into this issues and questions.
BR,
Vitthal
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
