Hello all,
I would like to call a vote on KIP-1153: Refactor Kafka Streams CloseOptions to
Fluent API Style
KIP:
<https://cwiki.apache.org/confluence/x/QAq9F>
Discussion thread:
<https://lists.apache.org/thread/zytvs28oq8fr8jpfro0w5q2tvs1308wo>
Best Regards,
Jiunn-Yang
ss that provides a getter method.
>
> Best Regards,
> Jiunn-Yang
>
>> Chia-Ping Tsai 於 2025年5月8日 下午1:55 寫道：
>>
>>> One more nit: we should remove the getters. There are useless. -- In
>> Kafka Streams, we follow the pattern to have a (non-public) sub-clas
Hi all,
Thanks for all the feedback. I’ve updated the KIP and introduced a
CloseOptionsInternal class that provides a getter method.
Best Regards,
Jiunn-Yang
> Chia-Ping Tsai 於 2025年5月8日 下午1:55 寫道：
>
>> One more nit: we should remove the getters. There are useless. -- In
> Ka
> One more nit: we should remove the getters. There are useless. -- In
Kafka Streams, we follow the pattern to have a (non-public) sub-class
`CloseOptionsInternal` which would add the necessary getters KS runtime
needs.
IIRC, we had a similar discussion regarding "internal" classes p
Thanks for updating the KIP.
One more nit: we should remove the getters. There are useless. -- In
Kafka Streams, we follow the pattern to have a (non-public) sub-class
`CloseOptionsInternal` which would add the necessary getters KS runtime
needs.
Cf
https://github.com/apache/kafka/blob
Thanks for the update! I think this is looking good now, my only feedback
would be to update the KIP title as well to reflect these latest changes.
Feel free to pick one yourself but if you want a suggestion, maybe
something like "Redo Kafka Streams CloseOptions in fluent style"
Alieh Saeedi created KAFKA-19244:
Summary: Add support for kafka-streams-groups.sh options beyond
list/describe group (delete group, offset-related APIs)
Key: KAFKA-19244
URL: https://issues.apache.org/jira
gt;>
>>>>>> public class CloseOptions {
>>>>>> public static CloseOptions timeout(Duration);
>>>>>> public static CloseOptions leaveGroup(boolean);
>>>>>>
>>>>>> public CloseOptions withTimeout(Du
[
https://issues.apache.org/jira/browse/KAFKA-18288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alieh Saeedi resolved KAFKA-18288.
--
Resolution: Fixed
> Add support kafka-streams-groups.sh --descr
t; > > >> enum a la KIP-1092 with valued DEFAULT, LEAVE_GROUP,
> REMAIN_IN_GROUP?
> > > >>
> > > >>
> > > >> Thoughts?
> > > >>
> > > >>
> > > >> -Matthias
> > > >>
> > > &g
gt; -Matthias
> > >>
> > >>
> > >>
> > >> On 4/25/25 3:05 PM, Sophie Blee-Goldman wrote:
> > >>> Thanks! I personally think this looks good, as we really just wanted
> to
> > >>> remove the public constructor, bu
ing Matthias to take a look
> and
> >>> make sure this is in line with his understanding
> >>>
> >>> If yes I think we can move to a vote
> >>>
> >>> On Fri, Apr 25, 2025 at 5:34 AM 黃竣陽 wrote:
> >>>
> >>>&
;>> If yes I think we can move to a vote
>>>
>>> On Fri, Apr 25, 2025 at 5:34 AM 黃竣陽 wrote:
>>>
>>>> Hello Sophie,
>>>>
>>>> Thanks for your comments,
>>>>
>>>> I’ve updated the KIP to add a new st
tatic `build()` method for
> initializing
> >> the CloseOptions object.
> >> The public constructor has been deprecated, while the existing
> >> fluent-style methods remain unchanged.
> >>
> >> Best Regards,
> >> Jiunn-Yang
> >>
&
KIP!
This looks good but a few comments about the API: I think we actually
want
more of a fluent pattern than a literal builder pattern, to be consistent
with other APIs in Kafka Streams. You can criticize Matthias for saying
"builder pattern" in the ticket, he means a fluent styl
iunn-Yang
>
> > Sophie Blee-Goldman 於 2025年4月25日 清晨5:15 寫道：
> >
> > Thanks for the KIP!
> >
> > This looks good but a few comments about the API: I think we actually
> want
> > more of a fluent pattern than a literal builder pattern, to be consistent
> >
於 2025年4月25日 清晨5:15 寫道：
>
> Thanks for the KIP!
>
> This looks good but a few comments about the API: I think we actually want
> more of a fluent pattern than a literal builder pattern, to be consistent
> with other APIs in Kafka Streams. You can criticize Matthias for saying
&
Thanks for the KIP!
This looks good but a few comments about the API: I think we actually want
more of a fluent pattern than a literal builder pattern, to be consistent
with other APIs in Kafka Streams. You can criticize Matthias for saying
"builder pattern" in the ticket, he means a fl
Matthias J. Sax created KAFKA-19171:
---
Summary: Kafka Streams crashes with UnsupportedOperationException
Key: KAFKA-19171
URL: https://issues.apache.org/jira/browse/KAFKA-19171
Project: Kafka
Hello everyone,
I would like to start a discussion on KIP-1153: Kafka Streams `CloseOptions`
should not have a public constructor
<https://cwiki.apache.org/confluence/x/QAq9F>
This proposal aims to improve KafkaStreams.CloseOptions by adopting a builder
pattern to ensure API consi
Alieh Saeedi created KAFKA-19128:
Summary: Kafka Streams should not get offsets when close dirty
Key: KAFKA-19128
URL: https://issues.apache.org/jira/browse/KAFKA-19128
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-18287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alieh Saeedi resolved KAFKA-18287.
--
Resolution: Fixed
https://github.com/apache/kafka/pull/19422
> Add support for kafka-stre
[
https://issues.apache.org/jira/browse/KAFKA-18287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna reopened KAFKA-18287:
---
> Add support for kafka-streams-groups.sh --l
[
https://issues.apache.org/jira/browse/KAFKA-18287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Cadonna resolved KAFKA-18287.
---
Resolution: Fixed
> Add support for kafka-streams-groups.sh --l
,
chAI
On 2025/04/01 18:58:40 Bill Bejeck wrote:
> Dear Apache Kafka Community,
> I'd like to propose an exciting new extension to the Kafka ecosystem that I
> believe will revolutionize how we think about stream processing:
> KStreamsJS-PHP - a full PHP implementation of Kafka Strea
>> Dear Apache Kafka Community,
> >> I'd like to propose an exciting new extension to the Kafka ecosystem
> >> that I
> >> believe will revolutionize how we think about stream processing:
> >> KStreamsJS-PHP - a full PHP implementation of Kafka St
Dear Apache Kafka Community,
I'd like to propose an exciting new extension to the Kafka ecosystem that I
believe will revolutionize how we think about stream processing:
KStreamsJS-PHP - a full PHP implementation of Kafka Streams with
browser-based AI capabilities.
Motivation
As we all know
Utku Aydin created KAFKA-19050:
--
Summary: kafka-streams-integration-tests artifact is empty
Key: KAFKA-19050
URL: https://issues.apache.org/jira/browse/KAFKA-19050
Project: Kafka
Issue Type
ad of leaving incompatible entires blank in Kafka
> Streams broker compatibility matrix
>
>
> Key: KAFKA-18195
> URL: https://issues.
> Components: kip, streams
>Reporter: Sebastien Viale
>Assignee: Sebastien Viale
>Priority: Minor
> Fix For: 4.1.0
>
>
> Jira to follow work on KIP:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-111
Matthias J. Sax created KAFKA-18943:
---
Summary: Kafka Streams incorrectly commits TX during task
revokation
Key: KAFKA-18943
URL: https://issues.apache.org/jira/browse/KAFKA-18943
Project: Kafka
introduces a blocking
bug for AK 4.0.
The issue is that the fix prevented Kafka Streams from re-initializing its
transactional producer under exactly-once semantics. That led to an infinite
loop of {{ProducerFencedException}}s with corresponding rebalances.
For example:
# 1 A network partitions
nt it out explicitly, since others
may have missed it as well, and it wasn't really discussed. In
retrospect, I would have objected to the WARN log, as any user
starting with a basic Kafka Streams example will be immediately
confronted with them. But it may be that I am the only one who mis
Rafał Sumisławski created KAFKA-18861:
-
Summary: kafka-streams stuck in a loop of "SyncGroup failed" with
an unbalanced assignment
Key: KAFKA-18861
URL: https://issues.apache.org/jira/browse/K
WARN log, as any user
starting with a basic Kafka Streams example will be immediately
confronted with them. But it may be that I am the only one who missed
it, in which case I’m okay with going forward with the KIP as
accepted.
Cheers,
Lucas
On Mon, Dec 16, 2024 at 8:56 AM Sebastien Viale
tuna b created KAFKA-18713:
--
Summary: Kafka Streams Left-Join not always emitting the last value
Key: KAFKA-18713
URL: https://issues.apache.org/jira/browse/KAFKA-18713
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-18498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Bejeck resolved KAFKA-18498.
-
Resolution: Fixed
> Kafka Streams main thread does not release l
thias
>
> On 1/21/25 2:01 AM, Ukpa Uchechi wrote:
> > Hi Kafka Dev Community,
> >
> > I’m currently working on updating the Kafka Streams documentation,
> > specifically the monitoring section. While reviewing the codebase, I
> > noticed that many of the descrip
dating the Kafka Streams documentation,
specifically the monitoring section. While reviewing the codebase, I
noticed that many of the descriptions are decoupled and defined in
different parts of the code, such as in statements like private static
final String DROPPED_RECORDS_TOTAL_D
Hi Kafka Dev Community,
I’m currently working on updating the Kafka Streams documentation,
specifically the monitoring section. While reviewing the codebase, I
noticed that many of the descriptions are decoupled and defined in
different parts of the code, such as in statements like private static
!
+1 (binding)
Cheers,
Lucas
On Wed, Nov 6, 2024 at 2:00 AM Bill Bejeck
wrote:
Hi All,
I'd like to call for a vote on KIP-1091
<
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1091%3A+Improved+Kafka+Streams+operator+metrics
(discussion t
Matthias J. Sax created KAFKA-18572:
---
Summary: Update Kafka Streams metric documenation
Key: KAFKA-18572
URL: https://issues.apache.org/jira/browse/KAFKA-18572
Project: Kafka
Issue Type
mjsax merged PR #661:
URL: https://github.com/apache/kafka-site/pull/661
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.or
Matthias J. Sax created KAFKA-18498:
---
Summary: Kafka Streams main thread does not release lock
Key: KAFKA-18498
URL: https://issues.apache.org/jira/browse/KAFKA-18498
Project: Kafka
Issue
JoinProcessor.java:101)
at
org.apache.kafka.streams.processor.internals.ProcessorNode.process(ProcessorNode.java:152)
... 19 more"
On Sun, 29 Dec 2024 at 09:45, Hagiu Alexandru wrote:
Hello,
I'm developing a Quarkus microservice that utilizes Kafka Streams to
process messages from multiple topics. Specifically, I'm
nals.ProcessorNode.process(ProcessorNode.java:152)
... 19 more"
On Sun, 29 Dec 2024 at 09:45, Hagiu Alexandru wrote:
> Hello,
>
> I'm developing a Quarkus microservice that utilizes Kafka Streams to
> process messages from multiple topics. Specifically, I'm attempting
mjsax opened a new pull request, #661:
URL: https://github.com/apache/kafka-site/pull/661
Cf https://github.com/apache/kafka/pull/18469
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specifi
Dead letter queue in Kafka Streams
Warning External sender Do not click on any links or open any attachments
unless you trust the sender and know the content is safe.
+1 (binding) on the updated KIP.
Thanks for the updates!
This email was screened for spam and malicious content but exercise ca
igned 5 years ago,
record timestamp was just newly added (and did not play a significant
role yet), and there was no record headers. That's why we have a
kv-based model with `KStream` and `KTable` types.
Given the changes in Kafka (and Kafka Streams) that accumulated over the
last 5 years, it seems
[
https://issues.apache.org/jira/browse/KAFKA-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-4437.
Resolution: Abandoned
> Incremental Batch Processing for Kafka Stre
uctionExceptionResponse
> >>> * DeserializationExceptionResponse
> >>> * ProcessingExceptionResponse
> >>>3.
> >>> I also propose nesting the class into the interface, as it is done
> >>> for enums.
> >>>
>
Seems this question was cross-posted on SO:
https://stackoverflow.com/questions/79299571/inconsistent-results-with-kstream-ktable-join-under-load
Left an answer there.
On 12/28/24 11:45 PM, Hagiu Alexandru wrote:
Hello,
I'm developing a Quarkus microservice that utilizes Kafka Strea
Hello,
I'm developing a Quarkus microservice that utilizes Kafka Streams to
process messages from multiple topics. Specifically, I'm attempting to join
a KStream and a KTable derived from two of these topics. Under normal
conditions, the join operates as expected. However, under incr
[
https://issues.apache.org/jira/browse/KAFKA-12822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-12822.
-
Resolution: Fixed
> Remove Deprecated APIs of Kafka Streams in
re 2024 09:06
À : dev@kafka.apache.org
Objet : [EXT] Re: [VOTE] KIP-1034: Dead letter queue in Kafka Streams
Warning External sender Do not click on any links or open any
attachments unless you trust the sender and know the content is safe.
Thanks Bill, Bruno, Sophie, I’ll conclude the vote wit
De : Bruno Cadonna
Envoyé : jeudi 19 décembre 2024 09:31
À : dev@kafka.apache.org
Objet : [EXT] Re: [DISCUSS] KIP-1034: Dead letter queue in Kafka Streams
Warning External sender Do not click on any links or open any attachments
unless you trust the sender and know the content is
ks
Sébastien
De : Matthias J. Sax
Envoyé : samedi 14 décembre 2024 05:29
À : dev@kafka.apache.org
Objet : [EXT] Re: [DISCUSS] KIP-1034: Dead letter queue in Kafka Streams
Warning External sender Do not click on any links or open any
attachments unless you trust the sender and know the con
: [DISCUSS] KIP-1034: Dead letter queue in Kafka Streams
Warning External sender Do not click on any links or open any attachments
unless you trust the sender and know the content is safe.
BC9: I did read up and play aroud a little bit. Enums do have a static
number which the compiler assings to them
De : Matthias J. Sax
Envoyé : samedi 7 décembre 2024 00:39
À : dev@kafka.apache.org
Objet : [EXT] Re: [VOTE] KIP-1034: Dead letter queue in Kafka Streams
Warning External sender Do not click on any links or open any
attachments unless you trust the sender and know the content is safe.
Thanks
Lucas Brutschy created KAFKA-18287:
--
Summary: Add support for kafka-streams-groups.sh --list
Key: KAFKA-18287
URL: https://issues.apache.org/jira/browse/KAFKA-18287
Project: Kafka
Issue
Lucas Brutschy created KAFKA-18288:
--
Summary: Add support kafka-streams-groups.sh --describe
Key: KAFKA-18288
URL: https://issues.apache.org/jira/browse/KAFKA-18288
Project: Kafka
Issue
, while
minimizing potential confusion or edge cases.
Thanks
Sébastien
De : Matthias J. Sax
Envoyé : samedi 14 décembre 2024 05:29
À : dev@kafka.apache.org
Objet : [EXT] Re: [DISCUSS] KIP-1034: Dead letter queue in Kafka Streams
Warning External sender Do not
-: Enforcing Explicit Naming for Kafka Streams
Internal Topics
Warning External sender Do not click on any links or open any attachments
unless you trust the sender and know the content is safe.
+1 (binding)
This email was screened for spam and malicious content but exercise caution
anyway.
On
quot;resume" instead of "continue," but I interpreted it as "let's
continue after stopping." If this is acceptable, I completely agree.
cheers
________
De : Bruno Cadonna
Envoyé : mercredi 11 décembre 2024 11:49
À : dev@kafka.apache.org
Objet : [EXT] Re: [DISCUSS] KIP-1034:
ut I interpreted it as "let's
continue after stopping." If this is acceptable, I completely agree.
cheers
________
De : Bruno Cadonna
Envoyé : mercredi 11 décembre 2024 11:49
À : dev@kafka.apache.org
Objet : [EXT] Re: [DISCUSS] KIP-1034: Dead letter q
C9
I wasn’t entirely happy with my naming either. I considered using
"resume" instead of "continue," but I interpreted it as "let's
continue after stopping." If this is acceptable, I completely agree.
cheers
________
De : Bruno Cadonna
Envo
di 11 décembre 2024 11:49
À : dev@kafka.apache.org
Objet : [EXT] Re: [DISCUSS] KIP-1034: Dead letter queue in Kafka Streams
Warning External sender Do not click on any links or open any attachments
unless you trust the sender and know the content is safe.
Hi,
Another suggestion came to
(binding)
Many Thanks!
Bruno
On 06.12.24 10:13, Lucas Brutschy wrote:
Thanks for the KIP!
+1 (binding)
Cheers,
Lucas
On Fri, Dec 6, 2024 at 9:41 AM Sebastien Viale
wrote:
Hi,
I'd like to start the vote on KIP- - Enforcing Explicit Naming for
Kafka Streams Internal Topics:
De : Sophie Blee-Goldman
Envoyé : mercredi 11 décembre 2024 23:56
À : dev@kafka.apache.org
Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka
Streams Internal Topics
Warning External sender Do not click on any links or open any attachments
unless
Envoyé : mercredi 11 décembre 2024 23:56
À : dev@kafka.apache.org
Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka
Streams Internal Topics
Warning External sender Do not click on any links or open any attachments
unless you trust the sender and know the content is safe.
Few
[
https://issues.apache.org/jira/browse/KAFKA-18015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-18015.
-
Resolution: Fixed
> Add duration based offset reset option for Kafka Stre
On Fri, Dec 6, 2024 at 9:41 AM Sebastien Viale
> > > wrote:
> > >>
> > >> Hi,
> > >>
> > >> I'd like to start the vote on KIP- - Enforcing Explicit Naming for
> > Kafka Streams Internal Topics:
> > >>
> >
;
> De : Matthias J. Sax
> Envoyé : vendredi 6 décembre 2024 23:45
> À : dev@kafka.apache.org
> Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka
> Streams Internal Topics
>
> Warning External sender Do not click on any lin
De : Bruno Cadonna
Envoyé : mercredi 11 décembre 2024 11:49
À : dev@kafka.apache.org
Objet : [EXT] Re: [DISCUSS] KIP-1034: Dead letter queue in Kafka Streams
Warning External sender Do not click on any links or open any attachments
unless you trust the sender and know the content is safe.
te:
Hi Bruno,
BC1
Make sense, let's keep this one outside of this KIP. I do think it
would make sense to have a more generic tool to reset topics. This
kind of stuff could be helpful, even outside of Kafka Streams (e.g.
DLQ in a Consumer application, while testing, etc...). Funnily, I h
De : Matthias J. Sax
Envoyé : samedi 7 décembre 2024 00:39
À : dev@kafka.apache.org
Objet : [EXT] Re: [VOTE] KIP-1034: Dead letter queue in Kafka Streams
Warning External sender Do not click on any links or open any attachments
unless you trust the sender and
ProductionExceptionHandler.Result.
Best,
Bruno
On 04.09.24 14:46, Damien Gasparina wrote:
Hi Bruno,
BC1
Make sense, let's keep this one outside of this KIP. I do think it
would make sense to have a more generic tool to reset topics. This
kind of stuff could be helpful, even outside of Kafka Streams
gt; +1 (binding)
> >
> > Cheers,
> > Lucas
> >
> > On Fri, Dec 6, 2024 at 9:41 AM Sebastien Viale
> > wrote:
> >>
> >> Hi,
> >>
> >> I'd like to start the vote on KIP- - Enforcing Explicit Naming for
> Kafka Streams Inte
is would avoid the need
> > > for another KIP in the future)
> > > StreamsUncaughtExceptionHandler
> > >
> > > - org.apache.kafka.streams.processor.api:
> > >
> > > ContextualFixedKeyProcessor
> > > ContextualProcessor
> > >
&g
Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka
Streams Internal Topics
Warning External sender Do not click on any links or open any attachments
unless you trust the sender and know the content is safe.
One last minor question:
You propose to add this new config with
A. Sophie Blee-Goldman created KAFKA-18195:
--
Summary: Enter "incompatible" instead of leaving incompatible
entires blank in Kafka Streams broker compatibility matrix
Key: KAFKA-18195
[
https://issues.apache.org/jira/browse/KAFKA-18067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-18067.
Resolution: Fixed
> Kafka Streams can leak Producer client under
Matthias J. Sax created KAFKA-18193:
---
Summary: Kafka Streams `CloseOptions` should not have a public
constructor
Key: KAFKA-18193
URL: https://issues.apache.org/jira/browse/KAFKA-18193
Project
also propose nesting the class into the interface, as it is done for enums.
cheers !
Sébastien
De : Matthias J. Sax
Envoyé : samedi 7 décembre 2024 00:39
À : dev@kafka.apache.org
Objet : [EXT] Re: [VOTE] KIP-1034: Dead letter queue in Kafka Streams
Warning
bastien
De : Damien Gasparina
Envoyé : vendredi 27 septembre 2024 09:06
À : dev@kafka.apache.org
Objet : [EXT] Re: [VOTE] KIP-1034: Dead letter queue in Kafka Streams
Warning External sender Do not click on any links or open any attachments
unless you trust the
that users reset their streams before enabling the
configuration.
Thanks for your feedback
Cheers
Sébastien
De : Bruno Cadonna
Envoyé : mardi 3 décembre 2024 09:14
À : dev@kafka.apache.org
Objet : [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-: Enf
Hi Sébastien,
+1 (binding)
Many Thanks!
Bruno
On 06.12.24 10:13, Lucas Brutschy wrote:
Thanks for the KIP!
+1 (binding)
Cheers,
Lucas
On Fri, Dec 6, 2024 at 9:41 AM Sebastien Viale
wrote:
Hi,
I'd like to start the vote on KIP- - Enforcing Explicit Naming for Kafka
Streams Int
Thanks for the KIP!
+1 (binding)
Cheers,
Lucas
On Fri, Dec 6, 2024 at 9:41 AM Sebastien Viale
wrote:
>
> Hi,
>
> I'd like to start the vote on KIP- - Enforcing Explicit Naming for Kafka
> Streams Internal Topics:
>
> https://cwiki.apache.org/confluence/display/K
Hi,
I'd like to start the vote on KIP- - Enforcing Explicit Naming for Kafka
Streams Internal Topics:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-%3A+Enforcing+Explicit+Naming+for+Kafka+Streams+Internal+Topics
This proposal aims to add a configuration that prevents a
vote to
> maintain transparency.
>
> Cheers,
> Loïc, Damien, and Sébastien
>
>
>
> De : Damien Gasparina
> Envoyé : vendredi 27 septembre 2024 09:06
> À : dev@kafka.apache.org
> Objet : [EXT] Re: [VOTE] KIP-1034: Dead letter qu
r your feedback
> >
> >
> > Cheers
> > Sébastien
> >
> >
> >
> >
> >
> >
> >
> > De : Bruno Cadonna
> > Envoyé : mardi 3 décembre 2024 09:14
> > À : dev@kafka.apache.org
> >
>
>
>
>
> De : Bruno Cadonna
> Envoyé : mardi 3 décembre 2024 09:14
> À : dev@kafka.apache.org
> Objet : [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-: Enforcing
> Explicit Naming for Kafka Streams Internal Topics
>
> Warning Th
Kafka Streams
Warning External sender Do not click on any links or open any attachments
unless you trust the sender and know the content is safe.
Thanks Bill, Bruno, Sophie, I’ll conclude the vote with your 3 binding votes.
Thank you everyone!
Damien
This email was screened for spam and
heers
Sébastien
De : Bruno Cadonna
Envoyé : mardi 3 décembre 2024 09:14
À : dev@kafka.apache.org
Objet : [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-: Enforcing
Explicit Naming for Kafka Streams Internal Topics
Warning This might be a fraudulent message! When click
ka.apache.org
Objet : [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-:
Enforcing Explicit Naming for Kafka Streams Internal Topics
Warning This might be a fraudulent message! When clicking REPLY, your
answers will NOT go to the sender (lbruts...@confluent.io.invalid).
Instead, replies w
. Nov. 2024, 13:40:
Hi everyone,
I would like to start a vote on KIP-655 which adds deduplication
processor
in kafka-streams:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-655%3A+Windowed+Distinct+Operation+for+Kafka+Streams+API
Thanks,
Ayoub
dup-interval
ts IS OLDER than stream-time minus de-dup interval though, we
could
also forward as "late"
What about different keys? What about different keys in combination
with
"late" records? Overall, I could not implement the logic base on
the KIP
as there is too
: jeudi 28 novembre 2024 11:51
À : dev@kafka.apache.org
Objet : [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-: Enforcing
Explicit Naming for Kafka Streams Internal Topics
Warning This might be a fraudulent message! When clicking REPLY, your answers
will NOT go to the sender (lbruts...@confl
sebastien.vi...@michelin.com would like to recall the message, "RE: [SUSPICIOUS
EXTERNAL MESSAGE] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka
Streams Internal Topics".
: [DISCUSS] KIP-: Enforcing
Explicit Naming for Kafka Streams Internal Topics
Warning This might be a fraudulent message! When clicking REPLY, your answers
will NOT go to the sender (lbruts...@confluent.io.invalid). Instead, replies
will be sent to dev@kafka.apache.org. Be cautious!
Hi all
1 - 100 of 2084 matches
Mail list logo
