Re: continuous query - changes from local server only

2018-02-08 Thread Som Som
i've got both client and server nodes on each of 3 physical servers, that is my cluster. there is a partitioned cache, each server node stores only a part of keys. i start the application on my dev machine that app is also client of the cluster further i put new key into the cluster. i would like

Re: @SpringApplicationContextResource / ApplicationContext / getBeansOfType()

2018-02-08 Thread Michael Cherkasov
Hi Navnet, Could you please share a reproducer for this issue? Some small mvn based project on github or as zip archive that will show the issue. Thanks, Mike. 2018-02-08 15:00 GMT-08:00 NK : > Hi, > > I have a Spring Boot app using Ignite 2.3.0. > > I am invoking

Re: continuous query - changes from local server only

2018-02-08 Thread dkarachentsev
Hi, You may fuse filter for that, for example: ContinuousQuery qry = new ContinuousQuery<>(); final Set nodes = new HashSet<>(client.cluster().forDataNodes("cache") .forHost(client.cluster().localNode()).nodes()); qry.setRemoteFilterFactory(new

Re: slow query performance against berkley db

2018-02-08 Thread Rajesh Kishore
Igniters any pointers pls. Regards, Rajesh On Wed, Feb 7, 2018 at 9:15 AM, Rajesh Kishore wrote: > Hi Dmitry, > > Thanks a ton. > > What is not convincing to me is with just *.1 M in main table and* *2 M > records in other table * , sql query is taking around 24 sec,

Re: Connecting Amazon cluster with client from local

2018-02-08 Thread rag1998
Reviving an old thread, since I am faced with a similar issue and am having trouble getting my head wrapped around it.. We recently started experimenting with Ignite and have a 2 server cluster setup on AWS with s3 based discovery, config for one of those servers looks like below: (The

ignite support for multii data center replication

2018-02-08 Thread Rajesh Kishore
Hi, Does Ignite replication works on Multi Data Center /WAN ? Regards, -Rajesh

Re: continuous query - changes from local server only

2018-02-08 Thread Vinokurov Pavel
Som, You could create the continuous query on each client node with the filter described above. 2018-02-08 19:55 GMT+03:00 Som Som <2av10...@gmail.com>: > i've got both client and server nodes on each of 3 physical servers, that > is my cluster. there is a partitioned cache, each server node

@SpringApplicationContextResource / ApplicationContext / getBeansOfType()

2018-02-08 Thread NK
Hi, I have a Spring Boot app using Ignite 2.3.0. I am invoking Ignite in a class called IgniteStarter using "IgniteSpring.start(springAppCtx)" where springAppCtx is my app's Spring Application Context. When I look for beans of a specific type in the main IgniteStarter class, I get the

Cat Example

2018-02-08 Thread Williams, Michael
Hi, Quick question, submitted a ticket earlier. How would I modify the below code such that, when viewed through Sql (dbeaver, eg) it behaves as if it had been created through a CREATE TABLE statement, where the name of the table was catCache? I'm trying to directly populate a series of tables

Re: Cat Example

2018-02-08 Thread Denis Magda
Hi Mike, If SQL indexes/configuration is set with the annotation and setIndexedTypes method then you have to use the type name (Cat in your case) as the SQL table name. It’s explained here: https://apacheignite-sql.readme.io/docs/schema-and-indexes#section-annotation-based-configuration

Distributed transaction support in Ingnite

2018-02-08 Thread Prasad Bhalerao
Hi, Does ignite support distributed transaction in case of collocate computation? I started two ignite nodes and then pushed the data to cache using following code. Please check code as given below. In this code I am rolling back the transaction at the end of compute affinity run. But after

Re: Distributed transaction support in Ingnite

2018-02-08 Thread Ilya Lantukh
Hi Phasad, Your approach is incorrect, and function that you passed into ignite.compute().affinityRun(...) will be executed outside of transaction scope. If you want to execute your code on the affinity node to modify value in cache, you should use IgniteCache.invoke(...) method - it will be a