Re: JTA transactions in Iginte

Hi, I can't use write through approach. I will be doing CRUD batch operations on oracle tables to avoid frequent calls to db. Now to keep ignite cache and oracle db consistent I have to use JTA transaction. Note: I have also enabled ignite persistance. Can you please provide an example to configur

Re: Apache Ignite nightly release builds

Thanks, Denis. It should be added to the download page, I updated the ticket. On Sat, Mar 24, 2018 at 5:48 AM, Denis Magda wrote: > Created a JIRA ticket for that: > https://issues.apache.org/jira/browse/IGNITE-8040 > > -- > Denis > > On Fri, Mar 23, 2018 at 1:27 AM, Dmitriy Setrakyan > wrote:

Re: [2.4.0] Cluster unrecoverable after node failure

Thanks Arseny - I really appreciate your assistance! The config files that I use are included in the attached archive. ignite-replicated.zip Let me know if you need anything else, or any clarification? Below (fo

Re: How suppress Ignite log message

For the records, setting the sys property `IGNITE_QUIET=false` disable the output to the system output (a bit counterintuitive .. ) p On Fri, Mar 23, 2018 at 12:13 PM, Paolo Di Tommaso < paolo.ditomm...@gmail.com> wrote: > Hi all, > > I'm migrating an application version 1.6 to 2.4. > > I've no

COUNT DISTINCT could push down group expressions

Queries involving COUNT(DISTINCT ) could push down the expression + group by into the mapper. Not doing this This causes an explosion of data received by the the reducer. On moderately large tables this usually causes OOM but worse than that it's just infeasible to execute at all. In the example b

how to organize groups in cluster?

assume we a ignite cluster of nodes A,B,C, is it possible to create partion cache only on node A and node B, and use topic message to replicate data to node C for real-time query? if not, is it possible to create 2 independant clusters, cluster1 for node A+node B, cluster2 for node C, and let them