+1 for deprecation
--Yakov 2018-01-30 1:06 GMT+03:00 Valentin Kulichenko <valentin.kuliche...@gmail.com >: > +1 > > On Mon, Jan 29, 2018 at 8:31 AM, Andrey Mashenkov < > andrey.mashen...@gmail.com> wrote: > > > Vyacheslav, > > > > +1 for dropping @CacheLocalStore. > > Ignite have no support 2-phase commit for store and public API provides > no > > methods to users can easily implement it by themselves. > > > > > > > > > > On Mon, Jan 29, 2018 at 7:11 PM, Vyacheslav Daradur <daradu...@gmail.com > > > > wrote: > > > > > Hi Igniters, > > > > > > I've worked with Apache Ignite 3rd Party Persistent Storage tools > > recently. > > > > > > I found that use of CacheLocalStore annotation has hidden issues, for > > > example: > > > * rebalancing issues [1] > > > * possible data consistency issues [1] > > > * handling of CacheLocalStore on clients nodes [2] > > > > > > Valentin K. considers it necessary to make @CacheLocalStore deprecated > > > and remove. If we want to have a decentralized persistent storage we > > > should use Apache Ignite Native Persistence. > > > > > > If the community supports this decision I will create a new Jira issue. > > > > > > Any thoughts? > > > > > > [1] http://apache-ignite-developers.2346864.n4.nabble. > > > com/Losing-data-during-restarting-cluster-with- > > > persistence-enabled-tt24267.html > > > [2] http://apache-ignite-developers.2346864.n4.nabble. > com/How-to-handle- > > > CacheLocalStore-on-clients-node-tt25703.html > > > > > > > > > > > > -- > > > Best Regards, Vyacheslav D. > > > > > > > > > > > -- > > Best regards, > > Andrey V. Mashenkov > > >
