currently internal `Change` type in the public API. But if we do this,
> it would not be limited to a single operator.
>
>
> -Matthias
>
> On 10/8/20 1:41 PM, Javier Freire Riobo wrote:
> > You're right. The behavior is correct with the cache disabled.
> >
> &g
on't see the need for a new operator.
>
>
> -Matthias
>
>
> On 10/7/20 1:51 PM, Javier Freire Riobo wrote:
> > I have done a small demo example. I hope it serves as a clarification.
> >
> > https://github.com/javierfreire/KTableToKStreamTest
> >
> &
example? I don't
> understand the relationship between "the same event is received twice"
> and a "non-zero commit time".
>
>
> -Matthias
>
> On 10/6/20 6:25 AM, Javier Freire Riobo wrote:
> > Hi all,
> >
> > I'd like to propose these changes
Hi all,
I'd like to propose these changes to the Kafka Streams API.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-675%3A+Convert+KTable+to+a+KStream+using+the+previous+value
This is a proposal to convert a KTable to a KStream knowing the previous
value of the registry.
I also opened a
Hi,
My UID is javier.freire. I wanted to create a KIP to add to Kafka Streams
the ability to convert a changelog stream to a stream by computing the
value by comparing the old and new value of the record.
These are the changes:
