Re: InternalCacheTransactionManager2PC removed from public API

2019-04-17 Thread Jacob Barrett
> On Apr 17, 2019, at 9:26 AM, Charlie Black wrote: > > The way transactions are done in Geode there shouldn't be any artifacts on > the client side. > > For more info check out the chapter on transactions with Geode: > https://geode.apache.org/docs/guide/16/developing/transactions/JTA_transa

Re: InternalCacheTransactionManager2PC removed from public API

2019-04-17 Thread Charlie Black
The way transactions are done in Geode there shouldn't be any artifacts on the client side. For more info check out the chapter on transactions with Geode: https://geode.apache.org/docs/guide/16/developing/transactions/JTA_transactions.html On Fri, Apr 12, 2019 at 7:04 AM Jacob Barrett wrote: >

Re: InternalCacheTransactionManager2PC removed from public API

2019-04-12 Thread Jacob Barrett
Sorry for the delay. In the initial source grant it inadvertently in the public headers. Prior to the 1.x release of Geode Native it was move internal where it belongs. There is currently no way in Geode Native to get access to the two phases commit transaction manager. This is an oversight tha

Re: InternalCacheTransactionManager2PC removed from public API

2019-04-12 Thread Mario Ivanac
Hi, just reformulate this question. What is the way forward if we want to use 2PC with C++ geode native? Regards, Mario Šalje: Mario Ivanac Poslano: 26. ožujka 2019. 8:42:57 Prima: dev@geode.apache.org Predmet: InternalCacheTransactionManager2PC removed from