Re: SQL query performance with JOIN and ORDER BY or WHERE

Hi Ilya, unfortunately this also didn't help improving query performance. Not sure what else I can try. Or maybe it is expected? In my opinion it shouldn't take that long as the query without the ORDER BY clause is super fast. Since there is a index on the order field I would expect this should

RE: slow node discovering on Kubernetes

Hi Maxim, Not really, I haven’t used flannel plugin and I’m not quite sure about network recommendations as well. Well, besides something basic, like avoid stretching between multiple availability zones and some persistence tuning,Like disabling MMAP for WAL (IGNITE_WAL_MMAP=false) > The problem

Is Geo redundancy supported in Ignite

Hi, Is geo-redundancy supported in Ignite ? Can we bring up 2 clusters in different location(geo) and make one cluster as backup for another ? Basically can ignite cluster in different location act as a active/ passive setup ? If one of the cluster goes down due to some issue in one location,

Re: Re: SQL query performance with JOIN and ORDER BY or WHERE

Hello! I think you can try a (QUEUEID, STATUS) index. Or maybe a (STATUS, QUEUEID), probably makes sense to try both. Regards, -- Ilya Kasnacheev сб, 10 апр. 2021 г. в 00:22, : > The QUEUED field is a BIGINT that contains timestamp from > System.currentTimeMillis(), so it should be pretty

Re: Stand-alone Mode Ignite Installation

Hello! Can you please highlight any specific issues that you are facing? Regards, -- Ilya Kasnacheev сб, 10 апр. 2021 г. в 20:40, sri hari kali charan Tummala < kali.tumm...@gmail.com>: > Hi Ignite Users, > > Below we link is not working spark ignite standalone mode installation > page. > >

[2.10]If affinityKey is used as a where condition, cannot retrieve the result set

Hi team, test.zip Is a single node snapshot compressed file. Unzip the file to the work directory of ignite, and then use the example.xml start a node and activate the cluster. You will see a table called viewsortcontrol. Execute the following SQL, the result is normal: SELECT * FROM

Re: Persistent Atomic types

> Do I need to put a simple ICache.Put() inside a transaction? No. Individual entry operations are always atomic. Note that ICache has methods like PutIfAbsent(key, val), Replace(key, old, new), which are useful for conditional atomic updates without transactions and locks. - Transactions are the