Hi, So, in short, you want to have some data structure basically separate from Ignite that would just be using Ignite's SQL engine. Is that right? If so, LOCAL caches sound like the closest what Ignite has for this. I'm not sure if it would be much simpler if it didn't use Ignite's infrastructure, and I'd imagine it would be hard to add to Ignite design-wise (would it be an IgniteCache? how to mock all the functionality of the IgniteCache that's completely unrelated to such "super local" cache?)
In any case, adding this functionality seems to be a topic for [email protected] - I suggest you post a question there. Thanks, Stan -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
