I think what he means is that no files are being created.. We are doing some
tests with Ignite and we don't see any use of the cache, even when we load
more keys than fit in physical memory.
--
View this message in context:
We were directly Manipulating the Cache.Entry and it was
reflecting directly in the H2 Indexes.. Not sure if it's desired behavior or
not.. But a definite Gotcha
To fix this we just call VALUE = ingintecache.get(KEY) to retrieve the value
rather than getting it directly from the
I think this is a bug..
I have meetings most of today.. I will definitely get you a code Sample..
copyOnRead is set to true.
Will work around it and try to get you code examples later today..
Basically this is easy to re-produce though, all you have to do is do a
query and pull an object out
Working with an ignite cache and I leave the H2 Debug window open while I'm
working.. So what I have noticed happening is that when I change values in
an object, this is IMMEDIATELY changed in the H2 Database window, even if I
start a transaction.. Should this happen only when I get and put a
I am building an ORM/Graph Database on top of Ignite.. Just wanted to know if
it is best practice on machines to close a cache after using it. Is it safe
to keep a map of handles to a bunch of classes? Or should we close or bound
the Ignite Caches?
--
View this message in context:
It could be 100's or even 1000's of objects..
Say we have Object A is related to Object B we need a way of expressing the
association so that we can navigate from one to the other.
it's a many to many association type idea.. If we co-locate the association
cache with the source, then we cannot
We have an object that contain an array of long[] values
What I am trying to do is to find all of the objects that contain a value in
that array.. Kind of trying to simulate edges in a graph database.. We can
achieve this goal via link tables and SQL
Alternatively I was thinking of indexing the