Jenkins build is back to normal : Kafka » kafka-trunk-jdk11 #202

See

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #194

See Changes: [github] MINOR: KIP-584: Remove admin client facility to read features from controller (#9536) -- [...truncated 3.42 MB...] org.apache.kafka.st

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #193

See Changes: [github] KAFKA-10471 Mark broker crash during log loading as unclean shutdown (#9364) [github] KAFKA-10632; Raft client should push all committed data to state machines (#9482) -

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #201

See Changes: [github] KAFKA-10632; Raft client should push all committed data to state machines (#9482) -- [...truncated 3.45 MB...] org.apache.kafka.stream

[jira] [Resolved] (KAFKA-10343) Add IBP based ApiVersion constraint tests

[ https://issues.apache.org/jira/browse/KAFKA-10343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-10343. - Resolution: Won't Fix We are planning to work on a more long-term fix for this issue, see  > Ad

[jira] [Created] (KAFKA-10677) Complete fetches in purgatory immediately after raft leader resigns

Jason Gustafson created KAFKA-10677: --- Summary: Complete fetches in purgatory immediately after raft leader resigns Key: KAFKA-10677 URL: https://issues.apache.org/jira/browse/KAFKA-10677 Project: Ka

[jira] [Created] (KAFKA-10676) Decide whether Raft listener callback errors are fatal

Jason Gustafson created KAFKA-10676: --- Summary: Decide whether Raft listener callback errors are fatal Key: KAFKA-10676 URL: https://issues.apache.org/jira/browse/KAFKA-10676 Project: Kafka

[jira] [Resolved] (KAFKA-10632) Raft client should push all committed data to listeners

[ https://issues.apache.org/jira/browse/KAFKA-10632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-10632. - Resolution: Fixed > Raft client should push all committed data to listeners > --

Jenkins build is back to normal : Kafka » kafka-trunk-jdk11 #199

See

[jira] [Created] (KAFKA-10675) Error message from ConnectSchema.validateValue() should include the name of the schema.

Alexander Iskuskov created KAFKA-10675: -- Summary: Error message from ConnectSchema.validateValue() should include the name of the schema. Key: KAFKA-10675 URL: https://issues.apache.org/jira/browse/KAFKA-1067

[jira] [Created] (KAFKA-10674) Brokers should know the active controller ApiVersion after enabling KIP-590 forwarding

Boyang Chen created KAFKA-10674: --- Summary: Brokers should know the active controller ApiVersion after enabling KIP-590 forwarding Key: KAFKA-10674 URL: https://issues.apache.org/jira/browse/KAFKA-10674

Build failed in Jenkins: Kafka » kafka-2.6-jdk8 #46

See Changes: [github] KAFKA-10454 / (2.6) Update copartitionSourceGroups when optimization algorithm is triggered (#9468) -- [...truncated 6.33 MB...] org.apac

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #50

See Changes: [Manikumar Reddy] KAFKA-10669: Make CurrentLeaderEpoch field ignorable and set MaxNumOffsets field default to 1 -- [...truncated 6.87 MB...] org.a

[jira] [Created] (KAFKA-10673) ConnectionQuotas should cache interbroker listener name

David Mao created KAFKA-10673: - Summary: ConnectionQuotas should cache interbroker listener name Key: KAFKA-10673 URL: https://issues.apache.org/jira/browse/KAFKA-10673 Project: Kafka Issue Type:

Re: Permission for contribution

Done. On 11/2/20 11:04 AM, Rohit Deshpande wrote: > Hi Boyang, > My wiki id is rohitdeshaws > > Thanks, > Rohit > > On Thu, Oct 29, 2020 at 1:59 PM Rohit Deshpande > wrote: > >> I don't know how to create wiki id. I am following this documentation: >> https://kafka.apache.org/contributing >> >

Re: Permission for contribution

Hi Boyang, My wiki id is rohitdeshaws Thanks, Rohit On Thu, Oct 29, 2020 at 1:59 PM Rohit Deshpande wrote: > I don't know how to create wiki id. I am following this documentation: > https://kafka.apache.org/contributing > > On Thu, Oct 29, 2020 at 1:40 PM Boyang Chen > wrote: > >> Added you to

[jira] [Resolved] (KAFKA-10669) ListOffsetRequest: make CurrentLeaderEpoch field ignorable and set MaxNumOffsets field to 1

[ https://issues.apache.org/jira/browse/KAFKA-10669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-10669. --- Resolution: Fixed Issue resolved by pull request 9540 [https://github.com/apache/kafka/pull/9540] >

Re: [DISCUSS] Apache Kafka 2.7.0 release

Hi Manikumar, Thanks for the heads-up. -Bill On Sat, Oct 31, 2020 at 4:56 PM Manikumar wrote: > Hi Bill, > > We have found a couple of issues related to ListOffsetRequest : > https://issues.apache.org/jira/browse/KAFKA-10669 > These were introduced when we migrated the ListOffsetRequest reques

Re: [VOTE] KIP-661: Expose task configurations in Connect REST API

+1 non-binding Thanks Mickael. Tom On Fri, Oct 16, 2020 at 8:54 PM Gwen Shapira wrote: > I definitely needed this capability a few times before. Thank you. > > +1 (binding) > > On Thu, Sep 24, 2020 at 7:54 AM Mickael Maison > wrote: > > > > Hi, > > > > I'd like to start a vote on KIP-661: > >

Re: [DISCUSS] Apache Kafka 2.6.1 release

Hi, Quick update on 2.6.1: Last week, a bunch of fixes went in for KAFKA-10651 and KAFKA-10515. John also backported the Jenkinsfile so tests can run on 2.6. Now, we only have 1 PR waiting to be merged: https://github.com/apache/kafka/pull/9468 (KAFKA-10454). Once this is merged, I'll start the