Re: Streams group final result: EmitStrategy vs Suppressed

2024-04-15 Thread Ayoub
Hello,

*[Not sure if my email went through as I was not subscribed to this mailing
list. Here is my original email]*

I found that there are two ways to send only the final result of a windowed
groupBy, either using Suppressed
.untilWindowCloses
on the final KTable or EmitStrategy

on
the windowed stream.

I tried to compare both but didn't find differences in the result they give.

Are there any differences apart from the moment they are defined within the
pipeline. And is there any preference on using one or the other ?

Thanks,
Ayoub


Le ven. 12 avr. 2024 à 11:50, Ayoub  a écrit :

> Hello,
>
> I found that there are two ways to send only the final result of a
> windowed groupBy, either using Suppressed
> .untilWindowCloses
> on the final KTable or EmitStrategy
> 
>  on
> the windowed stream.
>
> I tried to compare both but didn't find differences in the result they
> give.
>
> Are there any differences apart from the moment they are defined within
> the pipeline. And Is there any preference on using one or the other ?
>
> Thanks,
> Ayoub
>


RE: [ANNOUNCE] Apache Kafka 3.6.2

2024-04-15 Thread Merie Komlofske
On 2024/04/05 06:06:29 Manikumar wrote:
> The Apache Kafka community is pleased to announce the release for
> Apache Kafka 3.6.2
>
> This is a bug fix release and it includes fixes and improvements from 28
JIRAs.
>
> All of the changes in this release can be found in the release notes:
> https://www.apache.org/dist/kafka/3.6.2/RELEASE_NOTES.html
>
>
> You can download the source and binary release (Scala 2.12 and Scala
2.13) from:
> https://kafka.apache.org/downloads#3.6.2
>
>
---
>
>
> Apache Kafka is a distributed streaming platform with four core APIs:
>
>
> ** The Producer API allows an application to publish a stream of records
to
> one or more Kafka topics.
>
> ** The Consumer API allows an application to subscribe to one or more
> topics and process the stream of records produced to them.
>
> ** The Streams API allows an application to act as a stream processor,
> consuming an input stream from one or more topics and producing an
> output stream to one or more output topics, effectively transforming the
> input streams to output streams.
>
> ** The Connector API allows building and running reusable producers or
> consumers that connect Kafka topics to existing applications or data
> systems. For example, a connector to a relational database might
> capture every change to a table.
>
>
> With these APIs, Kafka can be used for two broad classes of application:
>
> ** Building real-time streaming data pipelines that reliably get data
> between systems or applications.
>
> ** Building real-time streaming applications that transform or react
> to the streams of data.
>
>
> Apache Kafka is in use at large and small companies worldwide, including
> Capital One, Goldman Sachs, ING, LinkedIn, Netflix, Pinterest, Rabobank,
> Target, The New York Times, Uber, Yelp, and Zalando, among others.
>
> A big thank you for the following 40 contributors to this release!
> (Please report an unintended omission)
>
> Akhilesh Chaganti, Andrew Schofield, Anton Liauchuk, Bob Barrett,
> Bruno Cadonna, Cheng-Kai, Zhang, Chia-Ping Tsai, Chris Egerton, Colin
> P. McCabe, Colin Patrick McCabe, David Arthur, David Jacot, David Mao,
> Divij Vaidya, Edoardo Comar, Emma Humber, Gaurav Narula, Greg Harris,
> hudeqi, Ismael Juma, Jason Gustafson, Jim Galasyn, Joel Hamill, Johnny
> Hsu, José Armando García Sancio, Justine Olshan, Luke Chen, Manikumar
> Reddy, Matthias J. Sax, Mayank Shekhar Narula, Mickael Maison, Mike
> Lloyd, Paolo Patierno, PoAn Yang, Ron Dagostino, Sagar Rao, Stanislav
> Kozlovski, Walker Carlson, Yash Mayya
>
> We welcome your help and feedback. For more information on how to
> report problems, and to get involved, visit the project website at
> https://kafka.apache.org/
>
> Thank you!
>
>
> Regards,
>
> Manikumar
> Release Manager for Apache Kafka 3.6.2
>


Streams group final result: EmitStrategy vs Suppressed

2024-04-15 Thread Ayoub
Hello,

I found that there are two ways to send only the final result of a windowed
groupBy, either using Suppressed
.untilWindowCloses
on the final KTable or EmitStrategy

on
the windowed stream.

I tried to compare both but didn't find differences in the result they give.

Are there any differences apart from the moment they are defined within the
pipeline. And Is there any preference on using one or the other ?

Thanks,
Ayoub