Re: Async messaging

Look at the article about asynchronous support of Ignite[1]. You are need to use method .future(), synchronous result be always null at this case. [1]: http://apacheignite.gridgain.org/docs/async-support On Sat, Nov 5, 2016 at 11:47 PM, Daniel Stieglitz < dstiegl...@stainlesscode.com> wrote: >

Re: Killing a node under load stalls the grid with ignite 1.7

Hi, It should not be in CacheStore implementation, but i if you does not want re-write logic, do it asynchronously. On Thu, Nov 3, 2016 at 6:35 PM, bintisepaha wrote: > the problem is when I am in write behind for order, how do I access the > trade > object. its only

Re: Ignite Jdbc connection

i see it is because of client timeout. and has been resolved. thanks. On 6 November 2016 at 00:36, Anil wrote: > Hi Manu and All, > > Ignite jdbc connection is very slow for very first time even with data > source. > > Consecutive queries are very fast. queries with 1 mins

Question: When to use CacheConfiguration.setIndexedTypes()?

Support, In review of Ignite Documentation (1.7.0) , I have the following questions about the proper use of 'CacheConfiguration.setIndexedTypes' In the 'ignite-examples' that come with distribution, the 'Person' class is annotated as follows: //Person's annotations /** Person ID

Class objects are fetched as string when JDBC api is used

Hi, After adding data to cache, i am try to fetch it using JDBC api and below statement - *rs = conn.createStatement().executeQuery("select * from SalesModel where _key=" + storeId);* Issue: Values other than class objects is retrieved correctly but class objects are taken as strings as shown