Re: KTable send old values API

Hi Michael, Thanks for reviewing and for the link. As I understand your post, especially > My question is: how much of the TTL idea is about (1) a more granular, per-key expiration of state than what we currently provide, vs. (2) decision-making for whether or not another downstream update shoul

Re: KTable send old values API

Dmitry, I think your use case is similar to the one I described in the link below (discussion in the kafka-dev mailing list): http://search-hadoop.com/m/uyzND1rVOQ12OJ84U&subj=Re+Streams+TTLCacheStore Could you take a quick look? -Michael On Wed, Feb 22, 2017 at 12:39 AM, Dmitry Minkovsky w

Re: KTable send old values API

Hi Eno, Thank you. I don't think I'm advanced enough to imagine a good API. But I can elaborate my use-cases further. So say I have two tables: KTable left = topology.table(stringSerde, stringSerde, topicLeft, topicLeft); KTable right = topology.table(stringSerde, stringSerde, to

Re: KTable send old values API

Hi Dmitry, Could you tell us more on the exact API you'd like? Perhaps if others find it useful too we/you can do a KIP. Thanks Eno > On 21 Feb 2017, at 22:01, Dmitry Minkovsky wrote: > > At KAFKA-2984: ktable sends old values when required >