Thanks for the quick reply, Val. To clarify the specific criteria, the "query consistency" guarantee specifically refers to transactions started (txStart) as either READ_REPEATABLE or SERIALIZABLE, and uses the put() and get() APIs; correct?
On Fri, Jul 7, 2017 at 3:13 PM vkulichenko [via Apache Ignite Users] < [email protected]> wrote: > Hi Jeff, > > Transactional consistency and MVCC is (and always will be) available only > for transactional caches. But for queries MVCC is not supported at all yet. > Queries are not enlisted in transactions and therefore you can get dirty > reads. Full support will be added by the end of the year (hopefully). > > -Val > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://apache-ignite-users.70518.x6.nabble.com/Does-the-Query-Consistency-feature-use-MVCC-tp14497p14507.html > To unsubscribe from Does the "Query Consistency" feature use MVCC?, click > here > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=14497&code=amVmZi5sYXZlckBnbWFpbC5jb218MTQ0OTd8LTE5MjU3ODI1NDQ=> > . > NAML > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Does-the-Query-Consistency-feature-use-MVCC-tp14497p14510.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
