Hi, MVCC + Transactional SQL will be available in the GA mode ~ Q3-Q4. Presently, we tell it loud and clear in our docs that transactions are supported for key-value APIs only.
-- Denis On Fri, Jun 1, 2018 at 5:12 AM, UCDeveloper <[email protected]> wrote: > We are planning to use the Apache Ignite inmemory database as a replacement > for the RDBMS that we are currently using. > > I am using the IgniteJdbcThinDriver to query/modify data on the database. > Though the queries are executed within a transaction scope , they are > actually getting executed in the atomic mode and hence the rollbacks are > not > working. > Found out from the documentation that this was a known issue and that the > feature would be available in v2.5. So I tried with the latest Ignite > version (v 2.5) but that didn't work either. > > Since the documentation mentions that the Ignite inmemory database is > transactional, is there any fix or some other solution to the issue that we > can implement to achieve this, using Ignite ? This feature is crucial for > us and any help would be appreciated. > > Thanks > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
