[jira] [Created] (KAFKA-12845) Rollback change which requires join key to be non null on KStream->GlobalKTable

Pedro Gontijo created KAFKA-12845: - Summary: Rollback change which requires join key to be non null on KStream->GlobalKTable Key: KAFKA-12845 URL: https://issues.apache.org/jira/browse/KAFKA-12845

Re: [VOTE] KIP-743: Remove config value 0.10.0-2.4 of Streams built-in metrics version config

+1 (binding) Thanks, Bruno! -John On Fri, May 21, 2021, at 10:58, Sophie Blee-Goldman wrote: > +1 (binding) > > Thanks Bruno! > > On Fri, May 21, 2021 at 8:06 AM Guozhang Wang wrote: > > > +1, thanks! > > > > On Fri, May 21, 2021 at 12:45 AM Bruno Cadonna wrote: > > > > > Hi, > > > > > >

Re: [VOTE] KIP-741: Change default serde to be null

+1 (binding) from me. Thanks for the KIP! -John On Mon, May 24, 2021, at 18:10, Sophie Blee-Goldman wrote: > +1 binding > > thanks for the KIP > -Sophie > > On Mon, May 24, 2021 at 2:02 PM Walker Carlson > wrote: > > > +1 (non-binding) from me, Leah > > > > Walker > > > > On Mon, May 24, 2021

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

See

Re: [VOTE] KIP-741: Change default serde to be null

+1 binding thanks for the KIP -Sophie On Mon, May 24, 2021 at 2:02 PM Walker Carlson wrote: > +1 (non-binding) from me, Leah > > Walker > > On Mon, May 24, 2021 at 1:51 PM Leah Thomas > wrote: > > > Hi, > > > > I'd like to kick-off voting for KIP-741: Change default serde to be null. > > < >

[jira] [Created] (KAFKA-12844) KIP-740 follow up: clean up TaskId

A. Sophie Blee-Goldman created KAFKA-12844: -- Summary: KIP-740 follow up: clean up TaskId Key: KAFKA-12844 URL: https://issues.apache.org/jira/browse/KAFKA-12844 Project: Kafka Issue

[jira] [Created] (KAFKA-12843) KIP-740 follow up: clean up TaskMetadata

A. Sophie Blee-Goldman created KAFKA-12843: -- Summary: KIP-740 follow up: clean up TaskMetadata Key: KAFKA-12843 URL: https://issues.apache.org/jira/browse/KAFKA-12843 Project: Kafka

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

See Changes: -- [...truncated 341524 lines...] [2021-05-24T19:36:26.090Z] > Task :connect:api:compileJava UP-TO-DATE [2021-05-24T19:36:26.090Z] > Task :connect:api:classes

Re: [VOTE] KIP-741: Change default serde to be null

+1 (non-binding) from me, Leah Walker On Mon, May 24, 2021 at 1:51 PM Leah Thomas wrote: > Hi, > > I'd like to kick-off voting for KIP-741: Change default serde to be null. > < > https://cwiki.apache.org/confluence/display/KAFKA/KIP-741%3A+Change+default+serde+to+be+null > > > The > discussion

Re: [VOTE] KIP-741: Change default serde to be null

+1, thanks! On Mon, May 24, 2021 at 1:51 PM Leah Thomas wrote: > Hi, > > I'd like to kick-off voting for KIP-741: Change default serde to be null. > < > https://cwiki.apache.org/confluence/display/KAFKA/KIP-741%3A+Change+default+serde+to+be+null > > > The > discussion is linked on the KIP for

[VOTE] KIP-741: Change default serde to be null

Hi, I'd like to kick-off voting for KIP-741: Change default serde to be null. The discussion is linked on the KIP for context. Cheers, Leah

Re: [DISCUSS] KIP-655: Windowed "Distinct" Operation for KStream

Hey there, Ivan! In typical fashion, I'm going to make a somewhat outlandish proposal. I'm hoping that we can side-step some of the complications that have arisen. Please bear with me. It seems like `distinct()` is not fundamentally unlike other windowed "aggregation" operations. Your concern

Re: [DISCUSS] KIP-739: Block Less on KafkaProducer#send

Hi all, I agree that we should give users the option of having a fully async API, but I don't think external thread pools or queues are the right direction to go here. They add performance overheads and don't address the root causes of the problem. There are basically two scenarios where we

Re: [DISCUSS] KIP-618: Atomic commit of source connector records and offsets

Hi all, Wanted to note here that I've updated the KIP document to include the changes discussed recently. They're mostly located in the "Public Interfaces" section. I suspect discussion hasn't concluded yet and there will probably be a few more changes to come, but wanted to take the opportunity

Re: [VOTE] KIP-720 Deprecate MirrorMaker v1

Thanks, Ryanne. Can you add information about this way forward to the KIP? Also it would be good to clarify that this work needs to get done before removing MM1. best, Colin On Thu, May 20, 2021, at 16:00, Ryanne Dolan wrote: > Hey y'all, reviving this thread because it seems we have a way

[jira] [Created] (KAFKA-12842) Failing test: org.apache.kafka.connect.integration.ConnectWorkerIntegrationTest.testSourceTaskNotBlockedOnShutdownWithNonExistentTopic

John Roesler created KAFKA-12842: Summary: Failing test: org.apache.kafka.connect.integration.ConnectWorkerIntegrationTest.testSourceTaskNotBlockedOnShutdownWithNonExistentTopic Key: KAFKA-12842 URL:

Re: [DISCUSS] KIP-741: Change default serde to be null

If there are no further notes, I'll go ahead and start the voting thread today. Thanks, Leah On Thu, May 20, 2021 at 2:58 PM Leah Thomas wrote: > Thanks for finding that, Guozhang. Consistency seems like the best option > to me as well, for the time being. I updated the KIP with that detail >

[jira] [Created] (KAFKA-12841) NPE from the provided metadata in client callback in case of ApiException

Avi Youkhananov created KAFKA-12841: --- Summary: NPE from the provided metadata in client callback in case of ApiException Key: KAFKA-12841 URL: https://issues.apache.org/jira/browse/KAFKA-12841

[jira] [Created] (KAFKA-12840) Removing `compact` cleaning on a topic should abort on-going compactions

David Jacot created KAFKA-12840: --- Summary: Removing `compact` cleaning on a topic should abort on-going compactions Key: KAFKA-12840 URL: https://issues.apache.org/jira/browse/KAFKA-12840 Project:

Quota Metrics - byte-rate

Hi Everyone! I was hoping to get some clarity on the Quota Metric (byte-rate). Could someone explain that does this metric represent how many bytes have been throttled, or does it represent at maximum how many bytes can be produced/consumed. Also, please explain how to interpret this metric.

Re: [VOTE] KIP-699: Update FindCoordinator to resolve multiple Coordinators at a time

Hi Mickael, Thank you for your response! Will take a look at the draft PR later this week. Cheers, Sanjana On May 21, 2021, 10:26 AM -0700, Mickael Maison , wrote: > Hi Sanjana, > > Again I'm sorry for the delay. > I've opened a draft PR which hopefully will let you make progress on > KIP-709.