RE: public @interface Query

2019-11-22 Thread alexanderkor12
Hi, Take a look at the example in https://github.com/apache/ignite/tree/master/examples/src/main/java/org/apac he/ignite/examples/springdata The https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apac he/ignite/examples/springdata/PersonRepository.java has the @Query ann

RE: Ignite node failure after network issue

2019-10-28 Thread alexanderkor12
Yes, putting the jar files with the necessary classes into the classpath of all nodes should solve the serialization issue. You should see the following in your logs: [2019-10-28 14:52:29,893][INFO ][sys-stripe-7-#8%node1%][GridDeploymentLocalStore] Class locally deployed: class org.joda.time.c

RE: Query execution in ignite

2019-10-28 Thread alexanderkor12
In PARTITIONED mode SQL queries are executed over each node’s primary partitions only. Here is more information about distributed joins: https://apacheignite-sql.readme.io/docs/distributed-joins From: Prasad Bhalerao Sent: Saturday, October 26, 2019 12:25 AM To: user@ignite.apache

RE: Ignite node failure after network issue

2019-10-25 Thread alexanderkor12
Hi, Your discovery section is non-standard. You don't need to repeat the entries. Also best if you prepend the local/loopback ip to be on the safe side. :47500..47509 :47500..47509

RE: Query execution in ignite

2019-10-25 Thread alexanderkor12
Hi, If a query is executed against a fully REPLICATED data then Ignite will send it to a single cluster node and run it over the local data there. if a query is executed over a PARTITIONED data, then the execution flow will be the following: The query will be parsed and split i

RE: Invalidate specific cache partitions

2019-10-24 Thread alexanderkor12
Hi! You can use IgniteCache.close() -- https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#close-- Or IgniteCache.destroy() -- https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#destroy-- To close or destroy a specific

RE: Connection Refused in Scala Ignite Client (Help!)

2019-10-16 Thread alexanderkor12
You need to replace the ip finder on all nodes to use the s3 one. add the libraries from libs/optional/ignite-aws to your application's classpath. No file is required. From: sri hari kali charan Tummala Sent: Wednesday, October 16, 2019 8:10 PM To: user@ignite.apache.org; alexanderko...@gm

RE: Connection Refused in Scala Ignite Client (Help!)

2019-10-16 Thread alexanderkor12
Hi, Try using the S3 IP Finder: https://apacheignite-mix.readme.io/docs/amazon-aws#section-amazon-s3-based-discovery Thanks, Alex From: sri hari kali charan Tummala Sent: Wednesday, October 16, 2019

RE: REST API: passing custom POJOs

2019-10-10 Thread alexanderkor12
Hi REST can accommodate the following types: https://apacheignite.readme.io/docs/rest-api#section-data-types You can use a ConnectorMessageIntercetor to intercept all incoming/outgoing rest requests : https://apacheignite.readme.io/docs/rest-api#section-general-configuration (https://ignite.apac