Thanks for the feedback Bruno, Matthias, and Lucas! There is a decent amount but I'm going to try and just hit the major points as I would like to keep this change simple.
I've made corrections for the mistakes pointed out. Thanks for the suggestions everyone. The main sticking point seems to be with the method of signalling the restore behavior. It seems we can all agree with how the API should look with the default option we are adding. I think keeping the option to load directly from the topic into the store is a good idea. It is much more performant and could make a simple metric collector processor much simpler. I think something that Matthais said about creating a special class of processors for the global stores helps me think about the issue. I tend to fall into the category that we should keep global stores open to the possibility of having child nodes in the future. I don't really see the downside of having that as an option. It might not be best for a lot of cases, but something simple could be very useful to put in the PAPI. I like the idea of having a `GlobalStoreParameters` but only if we decide to make the processor need to extend an interface like 'GobalStoreProcessor`. If not that seems excessive. As of right now I don't see a better option than having a boolean flag for the reprocessOnRestore option. I expanded the description in the docs so I hope that helps. I am more than willing to take other ideas on it. thanks, Walker
