Re: Data consistency essentials explained

2019-12-09 Thread Ivan Pavlukhin
Thank you! пн, 9 дек. 2019 г. в 19:08, Alexei Scherbakov : > > Ivan, > > It's true. The article is relevant for upcoming 2.8 release. I've added a > remark on that. > > пн, 9 дек. 2019 г. в 15:44, Ivan Pavlukhin : > > > Alexei, > > > > Am I getting it right that the article is relevant for current

Re: Data consistency essentials explained

2019-12-09 Thread Alexei Scherbakov
Ivan, It's true. The article is relevant for upcoming 2.8 release. I've added a remark on that. пн, 9 дек. 2019 г. в 15:44, Ivan Pavlukhin : > Alexei, > > Am I getting it right that the article is relevant for current master > and there is no released Ignite versions with described behavior? Is

Re: Data consistency essentials explained

2019-12-09 Thread Ivan Pavlukhin
Alexei, Am I getting it right that the article is relevant for current master and there is no released Ignite versions with described behavior? Is it mentioned in the document? Should we do it? What do you think? вт, 3 дек. 2019 г. в 12:34, Alexei Scherbakov : > > Ivan, > > for me GG docs have mo

Re: Data consistency essentials explained

2019-12-03 Thread Alexei Scherbakov
Ivan, for me GG docs have more clear information on the subject. As soon as community will improve docs quality link could be changed back to Apache. сб, 30 нояб. 2019 г. в 17:22, Ivan Pavlukhin : > Alexei, > > > Ivan, the link is intentional. > > Could you please elaborate why is it fine to hav

Re: Data consistency essentials explained

2019-11-30 Thread Ivan Pavlukhin
Alexei, > Ivan, the link is intentional. Could you please elaborate why is it fine to have a such link? The referred document is out of community control. Do not we have a similar one in Ignite documentation? Should we discuss it in another mail thread? сб, 30 нояб. 2019 г. в 15:48, Alexei Scher

Re: Data consistency essentials explained

2019-11-30 Thread Alexei Scherbakov
Ivan, the link is intentional. Nikolai, the formatting looks ok to me. Feel free to change it however you like. чт, 28 нояб. 2019 г. в 09:53, Николай Ижиков : > Hello, Alex. > > I think we should improve article formatting - code highlight, fonts, etc. > > For now, it’s very hard to read it. > >

Re: Data consistency essentials explained

2019-11-27 Thread Николай Ижиков
Hello, Alex. I think we should improve article formatting - code highlight, fonts, etc. For now, it’s very hard to read it. Can you, please, do it? > 28 нояб. 2019 г., в 09:25, Ivan Pavlukhin написал(а): > > Alexei, > > Many thanks for that article! Really nice that now we have a document >

Re: Data consistency essentials explained

2019-11-27 Thread Ivan Pavlukhin
Alexei, Many thanks for that article! Really nice that now we have a document describing Ignite approach for data consistency. I think it is super important because it is not trivial and very Ignite specific. I believe lots of Ignite developers will learn something new from this document. By the

Re: Data consistency essentials explained

2019-11-27 Thread Denis Magda
Alex, Thanks a lot for putting your knowledge on paper. That's an invaluable contribution! Looping in the user community (will be interesting for those who use native persistence) and has just spread the word via Ignite twitter handle: https://twitter.com/ApacheIgnite/status/1199837055007612928

Re: Data consistency essentials explained

2019-11-27 Thread Anton Vinogradov
Great news, thanks! On Wed, Nov 27, 2019 at 11:29 AM Alexei Scherbakov < alexey.scherbak...@gmail.com> wrote: > Igniters, > > As a final action in my almost year long effort in repairing data > consistency related issues for transactional persistent caches I've > prepared an article explaining th

Data consistency essentials explained

2019-11-27 Thread Alexei Scherbakov
Igniters, As a final action in my almost year long effort in repairing data consistency related issues for transactional persistent caches I've prepared an article explaining the principles of achieving the consistency between partition copies for these scenarios [1] Comments and suggestions are w