[jira] [Resolved] (KAFKA-14279) Add 3.3.1 to broker/client and stream upgrade/compatibility tests

[ https://issues.apache.org/jira/browse/KAFKA-14279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-14279. - Resolution: Fixed > Add 3.3.1 to broker/client and stream upgrade/compatibility tests >

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

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.4 #34

See

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

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.4 #33

See

Re: [DISCUSS] KIP-896: Remove old client protocol API versions in Kafka 4.0

Hi, Ismael, Thanks for the reply. 2. Yes, that makes sense. Jun On Mon, Jan 9, 2023 at 11:26 AM Ismael Juma wrote: > Hi Jun, > > Thanks for the feedback. > > 1. Good question. I was looking at the IBP issue as more of an inter broker > protocol communication thing and hence I thought we'd

Re: [DISCUSS] KIP-890 Server Side Defense

Hey all, I've updated the KIP to incorporate Jason's suggestions. https://cwiki.apache.org/confluence/display/KAFKA/KIP-890%3A+Transactions+Server-Side+Defense 1. Use AddPartitionsToTxn + verify flag to check on old clients 2. Updated AddPartitionsToTxn API to support transaction batching 3.

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.4 #32

See Changes: -- [...truncated 521713 lines...] [2023-01-09T22:01:29.987Z] > Task :connect:api:publishMavenJavaPublicationToMavenLocal [2023-01-09T22:01:29.987Z] > Task

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

See

[GitHub] [kafka-site] edoardocomar merged pull request #475: add Edoardo to committer list

edoardocomar merged PR #475: URL: https://github.com/apache/kafka-site/pull/475 -- 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:

[GitHub] [kafka-site] edoardocomar commented on pull request #475: add Edoardo to committer list

edoardocomar commented on PR #475: URL: https://github.com/apache/kafka-site/pull/475#issuecomment-1376356579 > Approvals are not compulsory on kafka-site but typically it's still always best to get someone to take a look and approve. I've approved now, so feel free to merge. Thanks

[GitHub] [kafka-site] mimaison commented on pull request #475: add Edoardo to committer list

mimaison commented on PR #475: URL: https://github.com/apache/kafka-site/pull/475#issuecomment-1376283918 Approvals are not compulsory on kafka-site but typically it's still always best to get someone to take a look and approve. I've approved now, so feel free to merge. -- This is an

Re: [ANNOUNCE] New committer: Edoardo Comar

Congratulations, Edo! Regards, Rajini On Mon, Jan 9, 2023 at 10:16 AM Tom Bentley wrote: > Congratulations! > > On Sun, 8 Jan 2023 at 01:14, Satish Duggana > wrote: > > > Congratulations, Edorado! > > > > On Sun, 8 Jan 2023 at 00:15, Viktor Somogyi-Vass > > wrote: > > > > > > Congrats

Re: [DISCUSS] KIP-896: Remove old client protocol API versions in Kafka 4.0

Hi Jun, Thanks for the feedback. 1. Good question. I was looking at the IBP issue as more of an inter broker protocol communication thing and hence I thought we'd cover that as part of the KIP that modernizes that aspect (yet to be written). I filed a JIRA recently that shares some of the

[GitHub] [kafka-site] edoardocomar commented on pull request #475: add Edoardo to committer list

edoardocomar commented on PR #475: URL: https://github.com/apache/kafka-site/pull/475#issuecomment-1376140418 @mimaison @rajinisivaram I do not understand if I should squash and merge myself or ask for approval ... -- This is an automated message from the Apache Git Service. To

Re: [DISCUSS] KIP-896: Remove old client protocol API versions in Kafka 4.0

Hi, Ismael, Thanks for the KIP. A couple of comments. 1. Should we deprecate IBPs before 2.1 too? 2. There seem to be more requests than those listed in the KIP. Are they all introduced after 2.1? Thanks, Jun On Sat, Jan 7, 2023 at 5:13 PM Ismael Juma wrote: > Hi all, > > I updated the

Re: [VOTE] 3.3.2 RC1

Hey Chris, I started a run for the system tests. The commit is b66af662e6. I'll message you again with a link to the results when it is done. Probably at the end of the day today or tomorrow morning. Thanks, -- -José

Re: [VOTE] 3.3.2 RC1

+1 binding. I have checked signatures, given the javadocs a quick look, followed the quickstart for KRaft and run the tests. Thanks Chris for running the release. Tom On Mon, 9 Jan 2023 at 15:29, Chris Egerton wrote: > Hi all, > > Thanks to everyone who has tested and voted for the release

[jira] [Created] (KAFKA-14610) Publish Mirror Maker 2 offset syncs in task commit method

Chris Egerton created KAFKA-14610: - Summary: Publish Mirror Maker 2 offset syncs in task commit method Key: KAFKA-14610 URL: https://issues.apache.org/jira/browse/KAFKA-14610 Project: Kafka

[jira] [Resolved] (KAFKA-14609) Kafka Streams Processor API cannot use state stores

[ https://issues.apache.org/jira/browse/KAFKA-14609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-14609. - Resolution: Fixed Fixed by https://issues.apache.org/jira/browse/KAFKA-14388 > Kafka Streams

Re: [VOTE] 3.3.2 RC1

Hi all, Thanks to everyone who has tested and voted for the release so far! Since we only have two binding votes so far, I'll be keeping the vote thread open until we either discover a blocker that requires a new release candidate to be generated, or get a third binding vote. For anyone

Re: [VOTE] KIP-710: Full support for distributed mode in dedicated MirrorMaker 2.0 clusters

Yes, you are! Congrats again :) -John On Mon, Jan 9, 2023, at 08:25, Viktor Somogyi-Vass wrote: > Hey all, > > Now that I'm a committer am I allowed to change my non-binding vote to > binding to pass the KIP? :) > > On Thu, Nov 10, 2022 at 6:13 PM Greg Harris > wrote: > >> +1 (non-binding) >>

Re: [DISCUSS] KIP-709: Extend OffsetFetch requests to accept multiple group ids

Hi all, I was looking at the OffsetFetchRequest in the context of KIP-848 and I noticed something that I would like to discuss. In the current implementation, when a group is specified multiple times in the request, we ignore all occurrences but the last one. That is because all groups are put

[jira] [Created] (KAFKA-14609) Kafka Streams Processor API cannot use state stores

Philipp Schirmer created KAFKA-14609: Summary: Kafka Streams Processor API cannot use state stores Key: KAFKA-14609 URL: https://issues.apache.org/jira/browse/KAFKA-14609 Project: Kafka

Re: [VOTE] KIP-710: Full support for distributed mode in dedicated MirrorMaker 2.0 clusters

Hey all, Now that I'm a committer am I allowed to change my non-binding vote to binding to pass the KIP? :) On Thu, Nov 10, 2022 at 6:13 PM Greg Harris wrote: > +1 (non-binding) > > Thanks for the KIP, this is an important improvement. > > Greg > > On Thu, Nov 10, 2022 at 7:21 AM John Roesler

[jira] [Resolved] (KAFKA-14570) Problem description missing closing parenthesis symbol

[ https://issues.apache.org/jira/browse/KAFKA-14570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-14570. Fix Version/s: 3.5.0 Resolution: Fixed > Problem description missing closing

Re: [ANNOUNCE] New committer: Edoardo Comar

Congratulations! On Sun, 8 Jan 2023 at 01:14, Satish Duggana wrote: > Congratulations, Edorado! > > On Sun, 8 Jan 2023 at 00:15, Viktor Somogyi-Vass > wrote: > > > > Congrats Edoardo! > > > > On Sat, Jan 7, 2023, 18:15 Bill Bejeck wrote: > > > > > Congratulations, Edoardo! > > > > > > -Bill >