Hi, in our use case we need to run some C++ code (via JNI) whenever something is pushed into the local Ignite cache. In other words, we need to have Ignite in sync with C++ memory. We have a local listener that listens to EVT_CACHE_OBJECT_PUT events and executes the C++ code, so everything is fine while the node is running. However, we use native persistence, so after a node restart, the local cache is read from the disk but the C++ code hasn't been run for any cache entries, which means that Ignite and C++ memory are out of sync.
Iterating through the local cache entries is only possible once the node has already joined the cluster, but that's too late for us - it needs to be done before joining the cluster. I've managed to add a lifecycle bean event BEFORE_CLUSTER_JOIN (see http://apache-ignite-users.70518.x6.nabble.com/Register-listeners-before-joining-the-cluster-tc25944.html, a PR is hopefully coming soon), which is triggered before joining the cluster but at that point we cannot access the cache via ignite.cache(...). Is there a way to access all entries in the native persistence at that point or earlier? I'm also fine with modifying the Ignite source code if that's necessary (and simple enough), since we are just prototyping.
