Re: Utilization of ignite indexes in Order By clause

Hello! I imagine that Ignite's underlying H2 planner will not use two different indexes on a same table. So even if you want ORDER BY to use index, it should be the same index that you are filtering results with. So you should probably start your index from assetGroupId. Regards, -- Ilya Kasna

Re: Ignite Indexes

Hello! Regarding index order: Index order basically means that records in the data_idx1 index will be sorted by field1; if two records have the same field1 value, field3 will be used as sorting tier, and if both field1 and field3 are same, field2 will be used as sorting tier. Index is basically a

Ignite Indexes

Hi, I have gone through this link , but still have some doubts. Please check the following example. public class TestData @QuerySqlField private long id; @QuerySqlField(orderedGroups = {@QuerySqlField.Group(n

Re: Ignite Indexes are stored where??

Hi, Since version 2.0 all of the data and indexes are stored in off-heap memory: https://apacheignite.readme.io/v2.3/docs/durable-memory. Evgenii 2018-02-27 13:50 GMT+03:00 KR Kumar : > Hi Guys - This could be a dumb question but i think its version dependent, > so > let me ask this anyways? D

Ignite Indexes are stored where??

Hi Guys - This could be a dumb question but i think its version dependent, so let me ask this anyways? Does Ignite store indexes in heap or off heap by default?? Because when I am profiling the application, I see huge bunch of int arrays instantiated by Ignite and wondering what are they ?? I am c

Re: Ignite indexes and persistence

Yep. Four nodes running on ec2 with 2 gp2 ebs disks each (one for persistence and one for wal). Running loader on first node connecting to local host. The cache in question is using the data region included in this config included at the bottom. here is the query info: explain select count(*)

Re: Ignite indexes and persistence

Hi, Did you test on single node or cluster? Could you describe in more ditails and provide configs? On Wed, Feb 21, 2018 at 11:24 PM, lawrencefinn wrote: > I've been testing ignite durable memory with trying to load a lot more data > than I have configured for the dataregion, thereby using disk

Ignite indexes and persistence

I've been testing ignite durable memory with trying to load a lot more data than I have configured for the dataregion, thereby using disk for a lot of data. I was wondering how indexes get persisted to disk in this situation where more data exists than will fit in memory? Is there a way to config