Hi, MVCC in Ignite is targeted to provide transactional consistency guarantees. I suppose that with eventually consistent 3rd party store it would be impossible to give much guarantees in general. Do think that such eventually consistent store will be widely used? What kind of guarantees should it provide? Is it easy to use it properly? Currently we do not have answers to these questions. Feedback is appreciated.
Also I must say that MVCC feature is currently in beta stage and limitations are listed in documentation [1]. [1] https://apacheignite.readme.io/docs/multiversion-concurrency-control#section-other-limitations чт, 28 февр. 2019 г. в 22:34, xmw45688 <[email protected]>: > > Hi Ilya, > > It'd better if this was mentioned in Ignite Doc. > > It seems very limited if MVCC only supports the Ignite native persistence. > Yes, supporting MVCC in 3rd party persistence is challenging. However, do > we really need MVCC when the data from Cache (where MVCC already enabled) is > ready to write to a 3rd party persistence store. I think that an "eventual > consistence" for writing cached data into a 3rd persistence layer seems > sufficient when Ignite is used as cache stored, and the data in cache store > is persistent. > > Does Ignite have a plan to support MVCC in cache layer and write the data > from the cached store into a 3rd party persistence store with some limited > feature like "eventual consistence". > > Can some gurus shed some lights on this subject? > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ -- Best regards, Ivan Pavlukhin
