I've been reading Ignite official document and going through Ignite source code 
for a few while now.

From the source code, I see that Ignite can be a key/value store and the data 
is stored in a ConcurrentHashMap for every partition.
So, this is one copy of data in memory.

For Ignite SQL function, it seems like Ignite creates a H2 table in memory 
based on the fields user want to be query with SQL.
So, does it mean for every key with @QuerySqlField annotation, there will be 
two copies of data in memory (one in ConcurrentHashMap and one in in-memory H2 
table)?


Reply via email to