Re: Immutable Record with Kafka Stream

; to less than this minimum, therefore is not accepted. Even Windows#until > > javadoc specifies it: > > > > > > * Set the window maintain duration (retention time) in milliseconds. > > > > > > * This retention time is a guaranteed lower bound for how long a > > window will be maint

Re: Immutable Record with Kafka Stream

s retention time is a guaranteed lower bound for how long a > window will be maintained. > > > > For more info consider reading [this](https://github.com/ > confluentinc/examples/issues/76) issue. > > > > Regards, Jozef > > > > > > Sent from [ProtonMai

Re: Immutable Record with Kafka Stream

> > > Sent from [ProtonMail](https://protonmail.ch), encrypted email based in > Switzerland. > > > > Original Message > Subject: Re: Immutable Record with Kafka Stream > Local Time: February 24, 2017 7:11 PM > UTC Time: February 24, 2017 7:11 PM >

Re: Immutable Record with Kafka Stream

pted email based in Switzerland. Original Message Subject: Re: Immutable Record with Kafka Stream Local Time: February 24, 2017 7:11 PM UTC Time: February 24, 2017 7:11 PM From: tarop...@gmail.com To: users@kafka.apache.org Guozhang, thanks for the reply, but I'm

Re: Immutable Record with Kafka Stream

Guozhang, thanks for the reply, but I'm having trouble understanding, here's the statement from the document Windowing operations are available in the Kafka Streams DSL > , > where users can specify a *retenti

Re: Immutable Record with Kafka Stream

Hi Kohki, Note that Streams execute operations based on the "timestamp" of the record, i.e. in your case it is the "event time" not the processing time. When you received 00:00:00,metric,2 After the long pause, it is considered as a "late arrived record" which happens at 00:00:00 but received

Re: Immutable Record with Kafka Stream

Thanks for the info, however there's an alarming functionality, duplicate message is a tricky thing to manage.. I thought 'retention-period' could work for that purpose, however here's the result My TimeWindow is TimeWindows.of(6).until(6), And here's the input 00:00:00,metric,1 00:01:0

Re: Immutable Record with Kafka Stream

Hi Kohki, As you mentioned, this is expected behavior. However, if you are willing to tolerate some more latency, you can improve the chance that a message with the same key is overwritten by increasing the commit time. By default it is 30 seconds, but you can increase it: streamsConfiguration

Immutable Record with Kafka Stream

Hello Kafka experts I'm trying to do windowed aggregation with Kafka Stream, however I'm getting multiple messages for the same time window, I know this is an expected behavior, however I really want to have a single message for given time window. my test code looks like below builder.stream