There is always one copy stored in Ignite.
The key-value store keeps data and Ignite indexes it using B+trees. H2 calls
Ignite’s trees when prepares execution plans.
This is partially mentioned here [1] and there [2] you can read more about the
memory architecture.
[1] https://apacheignite.re
Hi Ray,
Ignite replaces H2 row object with its own stub.
So, when you ask for a field value, ignite get entry represented by the row
and get entry field according to configured mapping (via Queryentity [1] or
via annotations [2]).
Ignite stores data in serialized way, as every field can be accesse
So when I run a sql in h2 debug console, how does h2 get results from cache
store?
In other words, how does the key/value cache entry to h2 entry mapping work?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
You will have only one copy of data, tables are needed for correct H2 work.
When do some query, H2 builds a query plan that will be delegated to Ignite,
which underneath gets data from cache.
Thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
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,
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 functio
