Hi all, In this JIRA ticket: https://issues.apache.org/jira/browse/KAFKA-7663 it's documented that Global Stores are bypassed on restoration.
Consequently, the input topic to a Global Store needs to essentially be a changelog topic as the keys and values are copied directly into the store. I heard (perhaps in the Slack) a while ago that there was some conversation about removing the ability to supply a Processor to the Global Store to prevent users from tripping over that behavior. However, we currently rely on the Processor to notify other parts of our application that things have changed in the store (eg. for cache invalidation, metrics, etc). Obviously, we make sure to respect the semantics of how the processor+global store works for restoration etc... It seems to me like the fact that we can pass in a Processor is a public API contract, so it should be safe to rely on that...? Would it require a KIP to change the fact that we can pass in a Processor? How much deprecation notice would we have before we need to find a new solution? Thanks, Colt McNealy *Founder, LittleHorse.dev*
