Hi Dongjin, Thanks for the KIP!
Can you explain more about why the internal data structures of suppression should be queriable? The motivation just says that users might want to do it, which seems like it could justify literally anything :) One design point of Suppression is that if you wanted to query the “final state”, you can Materialize the suppress itself (which is why it needs the variant); if you wanted to query the “intermediate state”, you can materialize the operator immediately before the suppress. Example: ...count(Materialized.as(“intermediate”)) .supress(untilWindowClosed(), Materialized.as(“final”)) I’m not sure what use case would require actually fetching from the internal buffers. Thanks, John On Fri, Feb 14, 2020, at 07:55, Dongjin Lee wrote: > Hi devs, > > I'd like to reboot the discussion on KIP-508, which aims to support a > Materialized variant of KTable#suppress. It was initially submitted several > months ago but closed by the inactivity. > > - KIP: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-508%3A+Make+Suppression+State+Queriable > - Jira: https://issues.apache.org/jira/browse/KAFKA-8403 > > All kinds of feedback will be greatly appreciated. > > Best, > Dongjin > > -- > *Dongjin Lee* > > *A hitchhiker in the mathematical world.* > *github: <http://goog_969573159/>github.com/dongjinleekr > <https://github.com/dongjinleekr>linkedin: kr.linkedin.com/in/dongjinleekr > <https://kr.linkedin.com/in/dongjinleekr>speakerdeck: speakerdeck.com/dongjin > <https://speakerdeck.com/dongjin>* >
