Hi It is very easy for user to shoot himself in a foot... and they do it again and again.... e.g. like this one [1].
[1] http://apache-ignite-users.70518.x6.nabble.com/Data-Loss-while-upgrading-custom-jar-from-old-jar-in-server-and-client-nodes-td20505.html On Thu, Mar 8, 2018 at 11:28 PM, Dmitriy Setrakyan <[email protected]> wrote: > To my knowledge, the 2.4 release should have support for both persistence > mechanisms, native and 3rd party, working together. The release is out for > a vote already: > http://apache-ignite-developers.2346864.n4.nabble. > com/VOTE-Apache-Ignite-2-4-0-RC1-td27687.html > > D. > > On Mon, Feb 26, 2018 at 2:43 AM, Humphrey <[email protected]> wrote: > >> I think he means when *write-through* and *read-through* modes are >> enabled on >> the 3rd party store, data might be written/read to/from one of those >> persistence storage (not on both). >> >> So if you save data "A" it might be stored in the 3rd party persistence, >> and >> not in the native. When data "A" is not in the cache it might try to look >> it >> up from the native persistence, where it's not available. Same could >> happen >> with updates, if "A" was updated to "B" it could have changed in the 3rd >> party but when requesting for the data again you might in one case get "A" >> an other case "B" depending on the stores it reads the data from. >> >> At least that is what I understand from his consistency between both >> stores. >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> > >
