Re: Run sql query on key-value cache

2021-03-11 Thread rakshita04
How can we create indexes on our existing cache. As far as i could see on your portal no API support is available for C++ for creating indexes. does Query Entity automatically takes care of creating indexes? or we need to explicitly create indexes on our cache? if we need to explicitly create , c

Re: Cache group setting not taking effect

2021-03-11 Thread joaogoncalves1
Hi Ilya, Sorry for the delay, we have been heavy testing our cluster since we were able to set the cache groups. A difference between development and production configs was making me believe that cache groups setting didn't work, but it does. We have noticed some improvement in performance, but it

Re: Async operations in IA C# client appear dangeroud

2021-03-11 Thread Raymond Wilson
Just as a followup query: Are async Compute methods susceptible to a similar issue, and should have the same treatment using a ContinueWith()? Thanks, Raymond. On Thu, Mar 11, 2021 at 8:45 PM Raymond Wilson wrote: > Hi Pavel, > > Thanks for the quick response. > > We have trialled the Continue

Re: Run sql query on key-value cache

2021-03-11 Thread Stephen Darlington
Just using SQL doesn’t automatically make your query faster (though it might), but it does mean you can use things like indexes. To use SQL on a cache, you need to define Query Entities. See the sample code for an example: https://github.com/apache/ignite/blob/f37ec9eece4db627f2d5190e589f0522e4

Run sql query on key-value cache

2021-03-11 Thread rakshita04
Hi Team, We are using apache-ignite node for our C++ application. For one of the scenarios we need to get the result based on value of the the columns(which is not key field). If we do a getAll() on DB node then we have to linearly search the whole Database which is taking too much time in case of

Re: Ignite 2.8.1 : Fetched result set was too large.

2021-03-11 Thread Veena
Thanks Stephen for the quick response. We did tried this option increasing IGNITE_SQL_MERGE_TABLE_MAX_SIZE to 50 in IGNITE SERVER But we are still getting the same exception. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/