Ok, I've added our thoughts from this thread to the second stage of this task:
1. IGNITE-2378 <https://issues.apache.org/jira/browse/IGNITE-2378> Data loss Part 2. Add flexible DataLoss Policy. Improve dataLoss event with batch. Feel free to comment it with all new ideas you come across. As for now, I assume supporting possibility for batching of reset request to be a great point, I'm going to implement this way. Thanks everyone! On Thu, Jan 14, 2016 at 1:38 PM, Alexey Goncharuk < [email protected]> wrote: > Dmitriy, > > Are you suggesting that we need to pass partitions state to a topology > validator so that user needs to check it manually. I do not think this is > convenient for an end-user and like the approach with the policy that > Vladimir suggested better. > > Raul, > > I assume you want to add IgniteCacheEx interface? How one would get it? > Another thing that crossed my mind was that it may be more efficient to > reset the state of multiple caches simultaneously, so maybe we should add > this method to Ignite and pass a list of cache names? >
