Hello!
You can implement Binarylizable which will serialize your objects so that
your relevant k1 and k2 are stored as entries in BinaryObject.
You can then add QueryEntity to cache to be able to index them properly.
Regards,
--
Ilya Kasnacheev
чт, 15 нояб. 2018 г. в 01:33, Ramin Farajollah :
Thanks for your informative reply.
I looked at CacheQueryExample to be able to query by both unique (k1) and
non-unique (k2) keys.
I use an /AffinityKey/. However, k1 (unique key) and k2
(non-unique key) are not member variables, where I would have been able to
annotate them with
Hi,
Yes, to add a new item to a list value of second cache Ignite will have to
deserialize whole list (with all it's items) then add new item and then
serialize list again.
You can try to use BinaryObjects to avoid unnecessary deserialization of
list items [1].
Also note, k2 and k1 data will have
Hi,
Please help me structure the cache to store instances of a type, say T.
I'd like to cache the objects in two different ways:
1. By a unique key (k1), where the value is a single instance
2. By a non-unique key (k2), where the value is a list of instances
Please comment on my approach:
-
