Re: [DISCUSS] KIP-819: Merge multiple KStreams in one operation

Hi all, The Named-first variant seems pretty appealing: merge(Named named, KStream... streams) It doesn't align with the existing merge methods, but it does at least follow precedent set by the (now-deprecated) branch method [1]. A Collection-based alternative seems slightly less appealing,

Re: [DISCUSS] KIP-819: Merge multiple KStreams in one operation

My understand was, that the original proposal was to have: merge(KStream stream); merge(KStream... streams); Maybe I misunderstood. I am not really a fan of merge(KStream stream, KStream... streams); because it seem to break the `Collection` pattern. If I have a collection of

Re: [DISCUSS] KIP-660: Pluggable ReplicaPlacer

Hi Mickael, Thanks for the update. It answered my questions! Thank you. Luke On Wed, Mar 30, 2022 at 12:09 AM Mickael Maison wrote: > Hi Luke, > > Thanks for the feedback. > > 1. Thanks, fixed! > 2. Yes that's right. It's the same behavior for topic policies > 3. I've added details about how

[jira] [Created] (KAFKA-13782) Producer may fail to add the correct partition to transaction

Jason Gustafson created KAFKA-13782: --- Summary: Producer may fail to add the correct partition to transaction Key: KAFKA-13782 URL: https://issues.apache.org/jira/browse/KAFKA-13782 Project: Kafka

Re: [VOTE] KIP-812: Introduce another form of the `KafkaStreams.close()` API that forces the member to leave the consumer group

Hi Guozhang, Sorry for the late reply, I'd had a time-consuming event on my career. Now I'm more available. Let me complete this KIP in 3.3.0. Seungchan On Wed, Mar 23, 2022 at 7:51 AM Guozhang Wang wrote: > Hello Seung-chan, > > Just checking if you are still working to complete this KIP?

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.2 #13

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #816

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.0 #194

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.1 #98

See

Re: [DISCUSS] Apache Kafka 3.1.1

Hi Tom, When do you expect to publish the first RC? Ismael On Thu, Mar 10, 2022 at 1:27 AM Tom Bentley wrote: > I think I was supposed to publish the release plan at the same time as > calling the vote for the release. > Here it is: >

[jira] [Created] (KAFKA-13781) Ensure consistent inter-broker listeners in KRaft

Jason Gustafson created KAFKA-13781: --- Summary: Ensure consistent inter-broker listeners in KRaft Key: KAFKA-13781 URL: https://issues.apache.org/jira/browse/KAFKA-13781 Project: Kafka

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #815

See

[jira] [Created] (KAFKA-13780) Generate docs for Connect REST API

Mickael Maison created KAFKA-13780: -- Summary: Generate docs for Connect REST API Key: KAFKA-13780 URL: https://issues.apache.org/jira/browse/KAFKA-13780 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-13779) System test verifying key updates with TLS 1.3

Ismael Juma created KAFKA-13779: --- Summary: System test verifying key updates with TLS 1.3 Key: KAFKA-13779 URL: https://issues.apache.org/jira/browse/KAFKA-13779 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-660: Pluggable ReplicaPlacer

Hi Luke, Thanks for the feedback. 1. Thanks, fixed! 2. Yes that's right. It's the same behavior for topic policies 3. I've added details about how the mentioned scenarios could be addressed. The information required to make such decisions is not part of the Kafka cluster metadata so an external

Re: [DISCUSS] KIP-660: Pluggable ReplicaPlacer

Hi Ryanne, That's a good point! There's no value in having all implementations perform the same sanity checks. If the replication factor is < 1 or larger than the current number of registered brokers, the controller should directly throw InvalidReplicationFactorException and not call the

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

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.2 #12

See

Re: Subscribe to Kafka dev mailing list

Hi, To subscribe you need to send email to dev-subscr...@kafka.apache.org, not dev@ Full instructions: https://kafka.apache.org/contact Kind regards, Tom On Tue, 29 Mar 2022 at 01:29, 那一叶零落 <1664637...@qq.com.invalid> wrote: > Subscribe to Kafka dev mailing list

[jira] [Created] (KAFKA-13778) Follower broker also always execute preferred read-replica selection

zhaobo created KAFKA-13778: -- Summary: Follower broker also always execute preferred read-replica selection Key: KAFKA-13778 URL: https://issues.apache.org/jira/browse/KAFKA-13778 Project: Kafka

Re: [VOTE] KIP-824 Allowing dumping segmentlogs limiting the batches in the output

Thanks Mickael, the steps were in the wiki page, sorry for that!! I have just updated the wiki page, so the voting was finished and this KIP is adopted Best regards. On Tue, 29 Mar 2022 at 12:32, Mickael Maison wrote: > Hi Sergio, > > You've obtained 3 binding votes and over 72 hours have

[VOTE] KIP-813 Shared State Stores

I would like to start a vote on this one: https://cwiki.apache.org/confluence/display/KAFKA/KIP-813%3A+Shareable+State+Stores Cheers, D.

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.2 #11

See Changes: -- [...truncated 523580 lines...] [2022-03-29T10:47:29.987Z] > Task :connect:api:generateMetadataFileForMavenJavaPublication [2022-03-29T10:47:29.987Z] > Task

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

See Changes: -- [...truncated 522687 lines...] [2022-03-29T10:35:56.751Z] [2022-03-29T10:35:56.751Z]

Re: [VOTE] KIP-824 Allowing dumping segmentlogs limiting the batches in the output

Hi Sergio, You've obtained 3 binding votes and over 72 hours have passed so you can close the vote, it has passed! Edit your KIP and mark it as "Accepted" and move it into the Adopted KIPs table in https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals Thanks, Mickael

[jira] [Created] (KAFKA-13777) Fix FetchResponse#responseData: Assignment of lazy-initialized members should be the last step with double-checked locking

YunKui Lu created KAFKA-13777: - Summary: Fix FetchResponse#responseData: Assignment of lazy-initialized members should be the last step with double-checked locking Key: KAFKA-13777 URL:

[jira] [Created] (KAFKA-13776) Update rocksdb to support arm64 M1 Mac

Francis De Brabandere created KAFKA-13776: - Summary: Update rocksdb to support arm64 M1 Mac Key: KAFKA-13776 URL: https://issues.apache.org/jira/browse/KAFKA-13776 Project: Kafka

[jira] [Created] (KAFKA-13775) CVE-2020-36518 - Upgrade jackson-databind to 2.12.6.1

Edwin Hobor created KAFKA-13775: --- Summary: CVE-2020-36518 - Upgrade jackson-databind to 2.12.6.1 Key: KAFKA-13775 URL: https://issues.apache.org/jira/browse/KAFKA-13775 Project: Kafka Issue

Re: [DISCUSS] KIP-819: Merge multiple KStreams in one operation

Yeah, the Named parameter makes it a little trickier. My suggestion would be to add an additional overload that looks like: KStream merged(KStream first, Named named, KStream rest); It's not ideal having the Named parameter split the other parameters; we could alternatively move the Named

[jira] [Resolved] (KAFKA-13767) Fetch from consumers should return immediately when preferred read replica is defined by the leader

[ https://issues.apache.org/jira/browse/KAFKA-13767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13767. - Reviewer: David Jacot Resolution: Fixed > Fetch from consumers should return immediately

Jenkins build became unstable: Kafka » Kafka Branch Builder » trunk #812

See