Hi Steve, The rational is simple - Ignite is a key-value storage. Locks, read and write operations, etc. - all done on per entry level, and applying optimizations like this would complicate things drastically, even if they are possible.
If you want to avoid duplication, you should normalize the data. I.e. if there are two objects referencing the same third object, store the latter as a separate entry, and save its key in first two (similar to foreign key in relational DB). You can then use SQL to query the data. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Identical-objects-on-the-same-node-tp11830p11841.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
