John Roesler created KAFKA-10540:
Summary: Convert KStream aggregations to new PAPI
Key: KAFKA-10540
URL: https://issues.apache.org/jira/browse/KAFKA-10540
Project: Kafka
Issue Type: Sub
John Roesler created KAFKA-10539:
Summary: Convert KStreamImpl joins to new PAPI
Key: KAFKA-10539
URL: https://issues.apache.org/jira/browse/KAFKA-10539
Project: Kafka
Issue Type: Sub-task
John Roesler created KAFKA-10538:
Summary: Convert KStreamImpl maps to new PAPI
Key: KAFKA-10538
URL: https://issues.apache.org/jira/browse/KAFKA-10538
Project: Kafka
Issue Type: Sub-task
John Roesler created KAFKA-10537:
Summary: Convert KStreamImpl filters to new PAPI
Key: KAFKA-10537
URL: https://issues.apache.org/jira/browse/KAFKA-10537
Project: Kafka
Issue Type: Sub-task
John Roesler created KAFKA-10536:
Summary: KIP-478: Implement KStream changes
Key: KAFKA-10536
URL: https://issues.apache.org/jira/browse/KAFKA-10536
Project: Kafka
Issue Type: Sub-task
John Roesler created KAFKA-10535:
Summary: KIP-478: Implement StateStoreContext and Record
Key: KAFKA-10535
URL: https://issues.apache.org/jira/browse/KAFKA-10535
Project: Kafka
Issue Type
Streams client will
> transit to ERROR if the last alive stream thread dies exceptionally.
> This corresponds to the current behavior.
>
> I will not restart voting and keep the votes so far.
>
> Best,
> Bruno
>
> On 22.09.20 01:19, John Roesler wrote:
> >
t;
> > I updated the PR applying the API changes we discussed above. I am now
> > updating the KIP document.
> >
> > Thanks,
> > Dongjin
> >
> > On Sat, Sep 19, 2020 at 10:42 AM John Roesler wrote:
> >
> >> Hi Dongjin,
> >>
> >
Thanks for the KIP, Walker!
I’m +1 (binding)
-John
On Mon, Sep 21, 2020, at 17:04, Guozhang Wang wrote:
> Thanks for finalizing the KIP. +1 (binding)
>
>
> Guozhang
>
> On Mon, Sep 21, 2020 at 1:38 PM Walker Carlson
> wrote:
>
> > Hello all,
> >
> > I would like to start a thread to vote fo
Hello all,
Thanks for bringing this up, Bruno. It’s a really good point that a
disconnected node would miss the signal and then resurrect a single-node
“zombie cluster” when it reconnects.
Offhand, I can’t think of a simple and reliable way to distinguish this case
from one in which an operato
Thanks, Jorge!
I’m +1 (binding)
-John
On Mon, Sep 21, 2020, at 12:35, Sophie Blee-Goldman wrote:
> Thanks for pointing out the vote in the discussion thread, this email
> somehow skipped my inbox ¯\_(ツ)_/¯
>
> I'm +1 (non-binding)
>
> -Sophie
>
> On Mon, Sep 7, 2020 at 4:18 AM Jorge Esteban
till +1, please vote again.
> >
> > Best,
> > Bruno
> >
> > On 04.09.20 23:12, John Roesler wrote:
> > > Hi Sophie,
> > >
> > > Uh, oh, it's never a good sign when the discussion moves
> > > into the vote thread :)
> >
Thanks for the KIP, Jorge!
Sorry it took me so long. I just reviewed the KIP, and it looks good to me.
Thanks,
John
On Tue, Sep 1, 2020, at 12:35, Jorge Esteban Quilcate Otoya wrote:
> Thanks Sophie!
>
> > one nit: you missed updating the startTime long to Instant in both
> appearances of the
l update the KIP by adding the discussion
> above.
>
> Best,
> Dongjin
>
> On Thu, Sep 17, 2020 at 11:06 AM John Roesler wrote:
>
> > Hi Dongjin,
> >
> > Thanks for the reply. Yes, that’s correct, we added that method to name
> > the operation. But
ason that you prefer the second
> approach?
>
> Thanks,
> Dongjin
>
> [^1]:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-307%3A+Allow+to+define+custom+processor+names+with+KStreams+DSL
>
>
>
> On Wed, Sep 16, 2020 at 11:48 PM John Roesler wrote:
>
fine API with the
> other related KIPs later.
>
> Do I understand correctly?
>
> Thanks,
> Dongjin
>
> On Wed, Sep 16, 2020 at 2:17 AM John Roesler wrote:
>
> > Hi Dongjin,
> >
> > Thanks for presenting these options. The concern that
> > Matthias broug
> >
> >
> > -Matthias
> >
> >
> > On 9/11/20 12:26 AM, Dongjin Lee wrote:
> > > Hi All,
> > >
> > > Here is the voting thread:
> > >
> >
> > https://lists.apache.org/thread.html/r5653bf2dafbb27b247
is case.
>
> Thus, for both cases, accessing the record context does not seems to be
> a requirement. And providing access to the processor context to, eg.,
> `forward()` or similar seems safe.
>
>
> -Matthias
>
> On 9/10/20 7:25 PM, John Roesler wrote:
> > Than
on’t want. So,
>
> restore for global store and get() might have to be exclusive. Is there a way
> for a
>
> store to know if it global store or not because now internally global and
> normal
>
> stores will behave differently. Although if everyone is fine with the above
Hello Sebastián,
Thanks for the question. I think the reason you don't find
documentation for this is that it's quite unusual to have a
data stream that just stops at some point and never sends
any more data.
Can you elaborate a little whether you meant that the whole
input topic just "ends" at s
t; Thanks for the help,
> -James
>
> > On Sep 11, 2020, at 12:53 PM, John Roesler wrote:
> >
> > Hi James,
> >
> > Sorry, I overlooked your reply until now. I've granted you
> > access.
> >
> > Thanks,
> > -John
> >
Hi James,
Sorry, I overlooked your reply until now. I've granted you
access.
Thanks,
-John
On Wed, 2020-09-09 at 21:44 -0700, James Cheng wrote:
> Thanks John. My wiki user ID is wushujames
>
> -James
>
> Sent from my iPhone
>
> > On Sep 9, 2020, at
Have you thought about whether it makes sense to support authorizing a
> > principal for a topic ID rather than a topic name to achieve tighter
> > security?
> >
> > Or is the topic ID fundamentally an internal detail similar to epochs used
> > in a bunch of other places in Kafk
Hello Justine,
Thanks for the KIP!
I happen to have been confronted recently with the need to keep track of a
large number of topics as compactly as possible. I was going to come up with
some way to dictionary encode the topic names as integers, but this seems much
better!
Apologies if this h
r previous response regarding the
> > range query after all. I thought you just meant a time-range query inside a
> > punctuator. It genuinely did not occur to me that users might be looking up
> > and/or updating records of other keys from within a Processor. Sorry for
> &
hat might be
> a valid use case or just a lurking bug in itself :)
>
> Thanks for humoring me. The current proposal for KIP-478 sounds good to me
>
> On Thu, Sep 10, 2020 at 3:43 PM John Roesler wrote:
>
> > Ah, thanks Sophie,
> >
> > I'm sorry for misint
lear use case I'd
> find
> that convincing. In the absence of any examples, the conservative approach
> sounds good to me.
>
> If it turns out that someone did need the record context in their custom
> state
> store, I'm sure they'll submit a politely worded
ore
> from their punctuator.
>
> Again, I think I do agree that we should leave the current record context
> off of
> the StateStoreContext, but I don't think the Punctuator argument against it
> is
> very convincing. It sounds to me like we need to disallow access to the
>
have a
> look after your work is done.
>
> Thanks,
> Dongjin
>
> On Sun, Mar 8, 2020 at 12:20 PM John Roesler wrote:
>
> > Thanks Matthias,
> >
> > Good idea. I've changed the ticket name and added a note
> > clarifying that this ticket is not th
store. But I can see some other
> things being useful, for example the current record's headers. Maybe if/when
> we add better (or any) support for headers in state stores this will be
> less true.
>
> Of course as John has made clear, it's pretty hard to judge withou
/org/apache/kafka/streams/state/internals/ChangeLoggingKeyValueBytesStore.java#L121
>
> You could have the writer client of the state store pass this through, but
> it would be nice to be able to write state stores where the client did not
> have this responsibility. I'm not s
atus of the JIRA to "Patch Available" if it's ready
> for review. Do this by clicking the "Submit Patch" button in JIRA, and
> then in the resulting dialog, click "Submit Patch".
>
> -James
>
> > On Sep 9, 2020, at 6:24 PM, John Roesl
Hi James,
I think the button on Jira says “Add Patch” or something confusing like that.
Thanks,
John
On Wed, Sep 9, 2020, at 17:34, James Cheng wrote:
> I have a JIRA that I am working on, and a pull request available for it.
>
> [KAFKA-10473] Website is missing docs on JMX metrics for partit
Hello all,
I've been slowly pushing KIP-478 forward over the last year,
and I'm happy to say that we're making good progress now.
However, several issues with the original design have come
to light.
The major changes:
We discovered that the original plan of just adding generic
parameters to Proc
John Roesler created KAFKA-10472:
Summary: Consider migrating Topology methods to the Builder pattern
Key: KAFKA-10472
URL: https://issues.apache.org/jira/browse/KAFKA-10472
Project: Kafka
Hello Jorge,
Thanks for the KIP!
FYI, it looks like there's still a boilerplate paragraph in
the KIP document about it being a template.
The KIP looks good to me; I'm +1 (binding) for doing this in
3.0.
Thanks,
-John
On Mon, 2020-09-07 at 12:18 +0100, Jorge Esteban Quilcate
Otoya wrote:
> Hi e
Hi Sophie,
Uh, oh, it's never a good sign when the discussion moves
into the vote thread :)
I agree with you, it seems like a good touch for
removeStreamThread() to return the name of the thread that
got removed, rather than a boolean flag. Maybe the return
value would be `null` if there is no th
een
> > the
> > > > two at all?
> > > > Would it make sense to avoid a special GLOBAL_RESTORING state and just
> > > > introduce
> > > > a single unified RESTORING state to cover both the regular and global
> > case?
> > > >
> > > Just thought of bumping this voting thread again to see if we can
> > > form
> > > > > any
> > > > > > consensus around this.
> > > > > >
> > > > > > Thanks!
> > > > > > Sagar.
>
ood to me as well, I added a few lines in the
> > KIP about logging an error when the *timeWindowedSerde *implicit is called.
> >
> > Let me know if there are any other concerns, else I'll resume voting.
> >
> > Cheers,
> > Leah
> >
> >
. Sax wrote:
> >
> > > Thanks for the KIP Yuriy!
> > >
> > > +1 (binding)
> > >
> > >
> > > -Matthias
> > >
> > > On 8/13/20 9:49 PM, John Roesler wrote:
> > > > Hi Yuriy,
> > > >
> > >
; > >
> > > I do feel like we would want to add an implicit to `Serdes.scala` that
> > > takes a serde and a window size so that users can access the constructor
> > > that initializes with the correct window size. I agree with your comment
> > on
> > > the K
Hi Sharath,
Please forgive me if this is a mistake, but I think I've
just granted this permission for your username "DOJI". Do
you need access as "DOJI45"?
Thanks,
-John
On Tue, 2020-09-01 at 16:11 +0530, Sharath Bhat wrote:
> Hi TeamPlease guide me on how I can request contributor access for ji
Hi Sandeep,
I've added you to the contributors group in Jira. Thanks for
your interest in Apache Kafka!
Thanks,
-John
On Tue, 2020-09-01 at 16:13 +0530, Sandeep Kumar wrote:
> Hi Team ,
>
> Please guide me how I can request for the contributor access for jira so
> that I can assign some jira ti
Hi Sharath,
I've added you to the contributor group in Jira. Thanks for
your interest in Apache Kafka!
Thanks,
-John
On Tue, 2020-09-01 at 17:22 +0530, Sharath Bhat wrote:
> Hi TeamPlease guide me on how I can request contributor access for jira so
> that i can assign some jira tickets to myself
Hi all,
Thanks for bringing this up, Jorge!
I'm not sure if we have a documented rule; I seem to recall
having had the same discussion for 2.0. My personal
suggestion would be to have a deprecation period of at least
one year, and beyond that to weigh how good we feel about
removing each deprecat
Hello Bruno,
Thanks for the update! The KIP looks good to me; I only have
a grammatical complaint about the proposed metric name.
"Died" is a verb, the past tense of "to die", but in the
expression,"x stream threads", x should be an adjective. To
be fair, "died" is also the past participle of "to
er to make progress on some
> tasks.
>
> Of course, if we collect real world experience and it becomes an issue,
> we could still try to change it?
>
>
> -Matthias
>
>
> On 8/18/20 3:31 PM, John Roesler wrote:
> > Thanks Matthias,
> >
> > Sounds go
[
https://issues.apache.org/jira/browse/KAFKA-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Roesler resolved KAFKA-10307.
--
Resolution: Not A Bug
This bug report was based on an invalid assumption that topologies
Thanks, Bruno!
I'm +1 (binding)
-John
On Thu, 2020-08-27 at 15:35 -0400, Bill Bejeck wrote:
> Thanks for the KIP Bruno.
>
> +1 (binding)
>
> -Bill
>
> On Thu, Aug 27, 2020 at 3:15 PM Walker Carlson
> wrote:
>
> > +1 (Non Binding). Good Kip Bruno
> >
> > Walker
> >
> > On Tue, Aug 25, 2020
Hi Bruno,
Thanks for the well motivated and throrough KIP!
It's a good point that the record cache should be re-
distributed over the threads.
Reading your KIP leads me to a few questions:
1. Start vs. Add
Maybe this is paranoid, but I'm mildly concerned that users
who don't read the docs too
Hi all,
I've just sent a new message to the DISCUSS thread. We
forgot to include the Scala API in the proposal.
Thanks,
-John
On Mon, 2020-08-24 at 18:00 -0700, Sophie Blee-Goldman
wrote:
> Thanks for the KIP! +1 (non-binding)
>
> Sophie
>
> On Mon, Aug 24, 2020 at 5:06 PM
s,
> Leah
>
> On Fri, Aug 21, 2020 at 2:50 PM John Roesler wrote:
>
> > Thanks, all,
> >
> > Based on my reading of the conversation, it sounds like I
> > have some legwork to do in KIP-645, but our collective
> > instinct is that Leah's proposal d
John Roesler created KAFKA-10437:
Summary: Convert test-utils (and StateStore) for KIP-478
Key: KAFKA-10437
URL: https://issues.apache.org/jira/browse/KAFKA-10437
Project: Kafka
Issue Type
John Roesler created KAFKA-10436:
Summary: Implement KIP-478 Topology changes
Key: KAFKA-10436
URL: https://issues.apache.org/jira/browse/KAFKA-10436
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-10379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Roesler resolved KAFKA-10379.
--
Resolution: Fixed
> Implement the KIP-478 StreamBuilder#addGlobalSt
Thanks Leah,
I’m +1 (binding)
-John
On Mon, Aug 24, 2020, at 16:54, Leah Thomas wrote:
> Hi everyone,
>
> I'd like to kick-off the vote for KIP-659: Improve
> TimeWindowedDeserializer
> and TimeWindowedSerde to handle window size.
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-659%3A+I
on Windows are handled separately from time
> > windows and also have variable window sizes. I assume that the TimeWindowed
> > option is preferable for variably sized windows because you still want to
> > access the window end times? But I think one alternative could be
>
Thanks for the KIP, Bruno!
Your proposal sounds good to me.
-John
On Fri, 2020-08-21 at 11:18 -0700, Sophie Blee-Goldman
wrote:
> Thanks for the KIP! I'm totally in favor of this approach and to be honest,
> have
> always wondered why we just silently shut down instead of throwing an
> exception
Hi Leah,
Thanks for the KIP! This has been a real pain for some use
cases, so it's really good to see a proposal to fix it.
We do need a default constructor so that it can be
dynamically instantiated by the consumer (or any other
component). But I'm +1 on deprecating the constructor you're
propos
dd a new state to KafkaStreams client for this case?
>
> Having a new state might also be helpful for
> https://issues.apache.org/jira/browse/KAFKA-7380 ?
>
>
>
> -Matthias
>
>
>
>
> On 8/17/20 7:34 AM, John Roesler wrote:
> > Hi Navinder,
> >
> >
ster, and we have already lost k1, k2 from the global
> topic so it will start consuming from the earliest point in the global topic.
> So, wouldn’t this global store on the new instance has 2 keys less than all
> the other global stores already available in the cluster? Please let
Thanks, Bill!
-John
On Thu, 2020-08-13 at 15:19 -0700, Ismael Juma wrote:
> Thanks for volunteering Bill. :)
>
> Ismael
>
> On Thu, Aug 13, 2020 at 3:13 PM Bill Bejeck wrote:
>
> > Hi All,
> >
> > I'd like to volunteer to be the release manager for our next feature
> > release, 2.7. If there
Thanks Mohamed,
I think Bruno raised a good point in the ticket that the
node name is not well known from within the Processor at the
time of init(), so users would basically have to make up a
name to pass into the sensor. Maybe this is ok, but it
doesn't seem too nice.
Offhand, it seems like the
Thanks Nikolay,
No objection. This would be very nice to have.
Thanks,
John
On Fri, Aug 14, 2020, at 09:18, Nikolay Izhikov wrote:
> Hello.
>
> > If anyone's interested in porting it to Python 3 it would be a good change.
>
> I’ve created a ticket [1] to upgrade system tests to python3.
> Do
If it's not good enough, we can
> still change the TimestampExtractor interface as a follow up?
>
>
> -Matthias
>
> On 7/28/20 10:03 AM, John Roesler wrote:
> > Thanks Matthias,
> >
> > This is a really good point. It might be a bummer
> > to have
>
> > > -Yuriy
> > >
> > > On Fri, Aug 7, 2020 at 8:10 AM Yuriy Badalyantc
> > wrote:
> > >
> > > > Hi everybody.
> > > >
> > > > There was some minor change since the voting process started (nullSerde
> > > > ad
for this or
> > just handling the reset in GlobalStreamThread should be sufficient?
> >
> > Regards,
> > Navinder
> >
> > On Tuesday, 7 July, 2020, 12:53:36 am IST, Matthias J. Sax
> > wrote:
> >
> > Atm, the config should be ign
atulations!
> > > >
> > > > > On Mon, Aug 10, 2020 at 1:11 PM Jun Rao wrote:
> > > > >
> > > > > Hi, Everyone,
> > > > >
> > > > > John Roesler has been a Kafka committer since Nov. 5, 2019. He has
> > > &
“Andy” Fang, Dima Reznik, Ego,
Evelyn Bayes, Ewen Cheslack-Postava, Greg Harris, Guozhang
Wang, Ismael Juma, Jason Gustafson, Jeff Widman, Jeremy
Custenborder, jiameixie, John Roesler, Jorge Esteban
Quilcate Otoya, Konstantine Karantasis, Lucent-Wong, Mario
Molina, Matthias J. Sax, Navinder Pal
John Roesler created KAFKA-10379:
Summary: Implement the KIP-478 StreamBuilder#addGlobalStore()
Key: KAFKA-10379
URL: https://issues.apache.org/jira/browse/KAFKA-10379
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Roesler resolved KAFKA-10261.
--
Resolution: Fixed
> Introduce the KIP-478 processors with sh
of values and deserialization.
>
> About Null serde - I'm ok with this. But, it should be a low priority
> implicit to not intersect will other implicits. I will add it.
>
> -Yuriy
>
> On Sat, Jul 11, 2020 at 9:18 PM John Roesler wrote:
>
> > Thanks, Yuriy,
Hello all,
This vote passes with four +1 votes (3 binding) and no 0 or -1 votes.
+1 votes
PMC Members (in voting order):
* Ismael Juma
* Manikumar Reddy
* Mickael Maison
Committers (in voting order):
* John Roesler
Community:
* No votes
0 votes
* No votes
-1 votes
* No votes
Vote thread
ified signatures, ran the tests on the source archive
> > > with
> > > Scala 2.13 and Java 11 and verified the quickstart with the source archive
> > > and Scala 2.13 binary archive.
> > >
> > > Ismael
> > >
> > > On Thu, Jul 23, 2020
g good and reasonable,
> > and the benefits are pretty clear.
> >
> > Haven't had a careful look through the POC yet but the proposal and
> > public changes you described sound great. Thanks for the KIP!
> >
> > On Tue, Jul 28, 2020 at 10:27 AM John Roesler
Congrats, Mickael!
-John
On Fri, Jul 31, 2020, at 23:29, Gwen Shapira wrote:
> Congratulations Mickael. Thrilled to have you as part of the PMC :)
>
> On Fri, Jul 31, 2020 at 8:14 AM Jun Rao wrote:
>
> > Hi, Everyone,
> >
> > Mickael Maison has been a Kafka committer since Nov. 5, 2019. He has
John Roesler created KAFKA-10336:
Summary: Rolling upgrade with Suppression AND Standbys may throw
exceptions
Key: KAFKA-10336
URL: https://issues.apache.org/jira/browse/KAFKA-10336
Project: Kafka
Hello again all,
Just a reminder that the 2.5.1 RC0 is available for verification.
Thanks,
John
On Thu, Jul 23, 2020, at 21:39, John Roesler wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the first candidate for release of Apache Kafka 2.5.1.
>
> Apa
[
https://issues.apache.org/jira/browse/KAFKA-9210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Roesler resolved KAFKA-9210.
-
Resolution: Fixed
> kafka stream loss data
> --
>
>
Hi John,
Thanks for picking this up! I’m +1 (binding).
-John
On Wed, Jul 29, 2020, at 09:14, Jorge Esteban Quilcate Otoya wrote:
> +1 (non-binding).
>
> Thanks John!
>
> On Wed, Jul 29, 2020 at 3:00 PM Navinder Brar
> wrote:
>
> > +1 (non-binding). Thanks John, looks good to me.
> >
> > ~Na
Thanks for the awesome KIP, Leah,
I’m +1 (binding)
Thanks,
John
On Tue, Jul 28, 2020, at 19:10, Guozhang Wang wrote:
> +1 (binding)
>
> On Tue, Jul 28, 2020 at 4:44 PM Matthias J. Sax wrote:
>
> > +1 (binding)
> >
> > On 7/28/20 4:35 PM, Sophie Blee-Goldman wrote:
> > > Thanks for the KIP! It
that sounds reasonable to you, I can update the
KIP accordingly.
Thanks,
-John
On Mon, Jul 27, 2020, at 22:11, John Roesler wrote:
> Thanks for the reply, Sophie.
>
> Yes, I'd neglected to specify that Windows will implement maxSize()
> by delegating to size(). It's updated
he
> >>> new API, could we try to address that? It should help with the motivation
> >>> and follow-up meta comments as John proposed.
> >>>
> >>> Boyang
> >>>
> >>> On Mon, Jul 6, 2020 at 12:04 PM Matthias J. Sax wrote:
&
John Roesler created KAFKA-10319:
Summary: Fix unknown offset sum on trunk
Key: KAFKA-10319
URL: https://issues.apache.org/jira/browse/KAFKA-10319
Project: Kafka
Issue Type: Sub-task
throughout the KIP but
> just to be clear,
> you will be replacing any DSL methods that accept Windows with identical
> DSL methods
> that take the new EnumerableWindowDefinition as argument. So there is
> nothing deprecated
> and nothing added, but there are public methods changed. Is t
olved by your proposal?
> >
> > By the way, I assume we would also need to deprecate all APIs that accept a
> > Windows
> > parameter in favor of new ones that accept a FixedSizeWindowDefinition? Off
> > the
> > top of my head that would be the windowedBy methods in KGroup
Thanks William,
I’m +1 (binding)
Thanks,
John
On Fri, Jul 24, 2020, at 20:22, Sophie Blee-Goldman wrote:
> Thanks all, +1 (non-binding)
>
> Cheers,
> Sophie
>
> On Wed, Jul 8, 2020 at 4:02 AM Bruno Cadonna wrote:
>
> > Thanks Will and Piotr,
> >
> > +1 (non-binding)
> >
> > Best,
> > Bruno
>
Hi Randall,
I'm sorry to say we have also identified that this flaky test
failure turned out to be a real blocker bug:
https://issues.apache.org/jira/browse/KAFKA-10287
There is a PR in progress.
Thanks,
-John
On Fri, Jul 24, 2020, at 12:26, Matthias J. Sax wrote:
> We found a regression bug th
9.05.20 10:00, Bruno Cadonna wrote:
> > Thank you for voting!
> >
> > This KIP passes with:
> > 4 binding +1
> > 1 non-binding +1
> > 0 -1
> >
> > Best,
> > Bruno
> >
> > On Fri, May 15, 2020 at 11:34 PM Matthias J. Sax w
Hello all,
Sorry again for the delay. While completing the RC, I found and had
to fix a broken system test. However, I've just created the vote thread
for 2.5.1 RC0! Please take a look at it and let me know what you think.
Thanks,
-John
On Tue, Jul 14, 2020, at 17:22, John Roesler
Hello Kafka users, developers and client-developers,
This is the first candidate for release of Apache Kafka 2.5.1.
Apache Kafka 2.5.1 is a bugfix release and fixes 72 issues since the 2.5.0
release. Please see the release notes for more information.
Release notes for the 2.5.1 release:
https:/
ake me nervous to go against the "future-proof" direction, though.
> Are there any other examples of things we might want to add to one window
> type but not to another?
>
> On another note, this actually brings up a new question: should
> SlidingWindows
> also be final?
ppens to be.
> >
> > Also, the fact that they can all rely on the same aggregation algorithm
> > seems like an
> > implementation detail and it would be weird to force a separate/new DSL API
> > just because
> > under the covers we swap in a different process
e put in a new window can be
> > found
> > >> on the implementation page
> > >> <
> > >>
> > https://cwiki.apache.org/confluence/display/KAFKA/Aggregation+details+for+KIP-450
> > >>>
> > >> .
> > >>
> > &g
Hello all,
I'd like to propose KIP-645, to correct a small API mistake in Streams.
Fixing this now allows us to avoid perpetuating the mistake in new work.
For example, it will allow us to implement KIP-450 cleanly.
The change itself should be seamless for users.
Please see https://cwiki.apache.
John Roesler created KAFKA-10298:
Summary: Replace Windows with a proper interface
Key: KAFKA-10298
URL: https://issues.apache.org/jira/browse/KAFKA-10298
Project: Kafka
Issue Type
gt; > on
> > >> the scheduled rocksdb metrics recorder whereas previously, we can
> > decide to
> > >> not turn on the recorder at all if all are set as DEBUG and we
> > configure at
> > >> INFO level in production. But this is an implementation det
[
https://issues.apache.org/jira/browse/KAFKA-10254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Roesler resolved KAFKA-10254.
--
Resolution: Fixed
Changing resolution to "fixed", since the linked duplicate is fix
[
https://issues.apache.org/jira/browse/KAFKA-10254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Roesler reopened KAFKA-10254:
--
> 100% cpu usage by kafkaConsumer poll , when broker can‘t be conn
401 - 500 of 1191 matches
Mail list logo
