[jira] [Resolved] (KAFKA-12640) AbstractCoordinator ignores backoff timeout when joining the consumer group

[ https://issues.apache.org/jira/browse/KAFKA-12640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-12640. - Resolution: Duplicate > AbstractCoordinator ignores backoff timeout when joining the

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #715

See

Re: [DISCUSS] KIP-820: Extend KStream process with new Processor API

For this KIP, I also see the value. I was just trying to make a step back and ask if it's a good short term solution. If we believe it is, I am fine with it. (I am more worried about the header's KIP...) Btw: I am still wondering if we can change existing `process()` as proposed in the KIP?

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #714

See Changes: -- [...truncated 368419 lines...] [2022-02-23T20:42:33.348Z] [2022-02-23T20:42:33.348Z] org.apache.kafka.streams.integration.TableTableJoinIntegrationTest >

Re: [DISCUSS] KIP-820: Extend KStream process with new Processor API

Hi folks, I agree with John that this KIP by itself could be a good improvement, and I feel it aligns well with the eventual DSL 2.0 proposal so we do not need to hold it until later. Regarding the last point (i.e. whether we should do enforcement with a new interface), here's my 2c: in the past

Re: [DISCUSS] KIP-794: Strictly Uniform Sticky Partitioner

Hi, Artem, Thanks for the reply. A few more comments. 1. Perhaps you could elaborate a bit more on how the producer determines the partition if the partitioner returns -1. This will help understand why encapsulating that logic as a partitioner is not clean. 2. I am not sure that I understand

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #713

See Changes: -- [...truncated 519384 lines...] [2022-02-23T17:08:24.221Z] [2022-02-23T17:08:24.221Z] org.apache.kafka.streams.integration.TableTableJoinIntegrationTest >

Re: [VOTE] KIP-815: Support max-timestamp in GetOffsetShell

Thanks for the KIP, Ziming! I'm +1 (binding) -John On Wed, 2022-02-23 at 13:54 +0100, Mickael Maison wrote: > Hi, > > I'm +1 (binding) too. > > Just one minor comment: > Could we make the "time" argument also accept "earliest", "latest" and > "max-timestamp" alongside -1, -2, -3. I think it's

Re: Call for review: KIP-618

Thanks Mickael! Looking forward to it. On Wed, Feb 23, 2022 at 8:54 AM Mickael Maison wrote: > Hi Chris, > > Thanks for taking the time to split this up. It would indeed be nice > to get this in 3.2. > > I've merged a couple of them already, and I'll make another pass in > the next few days. >

Re: Call for review: KIP-618

Hi Chris, Thanks for taking the time to split this up. It would indeed be nice to get this in 3.2. I've merged a couple of them already, and I'll make another pass in the next few days. Thanks, Mickael On Sat, Feb 19, 2022 at 12:32 AM Chris Egerton wrote: > > Thanks Luke! Appreciate it. > >

Re: [VOTE] KIP-815: Support max-timestamp in GetOffsetShell

Hi, I'm +1 (binding) too. Just one minor comment: Could we make the "time" argument also accept "earliest", "latest" and "max-timestamp" alongside -1, -2, -3. I think it's a bit confusing to use these negative numbers to specify the desired timestamps. Thanks On Tue, Feb 22, 2022 at 8:05 AM

[jira] [Resolved] (KAFKA-13685) Seems to get empty event time in some messages.

[ https://issues.apache.org/jira/browse/KAFKA-13685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex resolved KAFKA-13685. -- Resolution: Auto Closed > Seems to get empty event time in some messages. >

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #712

See Changes: -- [...truncated 518412 lines...] [Pipeline] } [2022-02-23T09:49:09.913Z] [2022-02-23T09:49:09.913Z]

[jira] [Created] (KAFKA-13689) AbstractConfig log print information is incorrect

RivenSun created KAFKA-13689: Summary: AbstractConfig log print information is incorrect Key: KAFKA-13689 URL: https://issues.apache.org/jira/browse/KAFKA-13689 Project: Kafka Issue Type: Bug