[jira] [Resolved] (KAFKA-14495) Improve the RemoteIndexCacheTest

[ https://issues.apache.org/jira/browse/KAFKA-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-14495. --- Fix Version/s: 3.5.0 Resolution: Fixed > Improve the RemoteIndexCacheTest >

[jira] [Resolved] (KAFKA-14128) Kafka Streams terminates on topic check

[ https://issues.apache.org/jira/browse/KAFKA-14128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-14128. - Fix Version/s: 3.5.0 3.4.1 Resolution: Fixed > Kafka Streams

Re: [DISCUSS] KIP-904 Kafka Streams - Guarantee subtractor is called before adder if key has not changed

Thanks for the KIP. Overall LGTM. I think you can start a VOTE. -Matthias On 2/22/23 5:56 PM, Fq Public wrote: Just wanted to bump this thread for visbility. Thanks to everyone who has participated in the discussion so far. Thanks, Farooq On 2023/02/14 19:32:53 Guozhang Wang wrote: Thanks

Re: [DISCUSS] KIP-907: Add Boolean Serde to public interface

Thanks for the KIP. Overall LGMT. One comment: Both `BooleanSerializer` and `BooleanDeserializer` are also new classes that are added and should be listed explicitly similar to `BooleanSerde` in the "Public Interfaces" section of the KIP. -Matthias On 2/21/23 10:52 AM, SpacRocket wrote:

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

See Changes: -- [...truncated 531604 lines...] [2023-02-23T00:40:01.542Z] [2023-02-23T00:40:01.542Z] Gradle Test Run :core:integrationTest > Gradle Test Executor 175 >

RE: RE: Re: Re: RE: Re: RE: Re: [DISCUSS] KIP-885: Expose Broker's Name and Version to Clients Skip to end of metadata

Pinging on this, to refresh any inboxes. On 2023/01/01 20:16:18 Travis Bischel wrote: > To confirm, you’re now thinking that we should add name + version to every > broker in the response? AFAICT, this grows the complexity of implementation a > good amount. The implementation of the current

RE: Re: Re: [DISCUSS] KIP-904 Kafka Streams - Guarantee subtractor is called before adder if key has not changed

Just wanted to bump this thread for visbility. Thanks to everyone who has participated in the discussion so far. Thanks, Farooq On 2023/02/14 19:32:53 Guozhang Wang wrote: > Thanks Farooq, that looks good to me. > > Guozhang > > On Sun, Feb 12, 2023 at 9:01 AM Dharin Shah wrote: > > > >

Re: [VOTE] KIP-890: Transactions Server Side Defense

Hey all, I've updated the KIP to slightly change some of the request and response specs for AddPartitionsToTxn. Nothing huge, but some points came up during PR review. https://cwiki.apache.org/confluence/display/KAFKA/KIP-890%3A+Transactions+Server-Side+Defense Thanks, Justine On Fri, Feb 3,

Re: [VOTE] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

Hi Calvin, The `BrokerState` struct I suggested would replace the `BrokerId` field in older versions. { "name": "ReplicaId", "type": "int32", "versions": "0-13", "entityType": "brokerId", "about": "The broker ID of the follower, of -1 if this request is from a consumer." }, {

[jira] [Resolved] (KAFKA-5827) Allow configuring Kafka sink connectors to start processing records from the end of topics

[ https://issues.apache.org/jira/browse/KAFKA-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-5827. Resolution: Duplicate > Allow configuring Kafka sink connectors to start processing records from

[jira] [Resolved] (KAFKA-4006) Kafka connect fails sometime with InvalidTopicException in distributed mode

[ https://issues.apache.org/jira/browse/KAFKA-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-4006. Fix Version/s: 0.11.0.0 Resolution: Fixed > Kafka connect fails sometime with

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

See

[jira] [Created] (KAFKA-14742) Flaky ExactlyOnceSourceIntegrationTest.testConnectorBoundary OOMs

Greg Harris created KAFKA-14742: --- Summary: Flaky ExactlyOnceSourceIntegrationTest.testConnectorBoundary OOMs Key: KAFKA-14742 URL: https://issues.apache.org/jira/browse/KAFKA-14742 Project: Kafka

Re: [VOTE] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

To Jose: 1. Actually I have a second thoughts about the naming ReplicaEpoch. The BrokerEpoch only applies to the replication protocol between the brokers. For others like the KRaft controller, this field can be ignored. So can we change the name to ReplicaEpoch when we really use it in other

Re: [VOTE] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

To Jason: 1. Related to the Fetch Request fields change, previously you suggested deprecating the ReplicaId and moving it into a BrokerState field. How about we just make the BrokerEpoch a tag field? - The ReplicaId is currently in use and is filled every time. So that we can keep the way simple.

Re: [VOTE] KIP-894: Use incrementalAlterConfigs API for syncing topic configurations

Thanks for the KIP! +1 binding On Wed, Feb 22, 2023 at 6:00 PM Chris Egerton wrote: > > +1 (binding). Thanks again, Tina! > > On Wed, Feb 22, 2023 at 2:02 AM Luke Chen wrote: > > > +1 (binding) from me. > > > > Thank you. > > Luke > > > > On Thu, Jan 26, 2023 at 11:24 PM Federico Valeri > >

Re: [VOTE] KIP-894: Use incrementalAlterConfigs API for syncing topic configurations

+1 (binding). Thanks again, Tina! On Wed, Feb 22, 2023 at 2:02 AM Luke Chen wrote: > +1 (binding) from me. > > Thank you. > Luke > > On Thu, Jan 26, 2023 at 11:24 PM Federico Valeri > wrote: > > > +1 (non binding) > > > > Thanks. > > > > On Thu, Jan 26, 2023 at 2:30 PM Gantigmaa Selenge > >

Re: [DISCUSS] solutions for broker OOM caused by many producer IDs

*Hi Justine, * *My initial thought of throttling the initProducerId was to get ripped off the problem at the source (which creates too many PIDs per client) and fail faster but if having this on the produce request level is easier this should be fine. I am guessing it will be the same direction

[jira] [Created] (KAFKA-14741) Add description field to connector configs

Mickael Maison created KAFKA-14741: -- Summary: Add description field to connector configs Key: KAFKA-14741 URL: https://issues.apache.org/jira/browse/KAFKA-14741 Project: Kafka Issue Type:

Re: Please help to create an JIRA account for me, thanks

Hi Koma, You're all set now. Note that JIRA only allows lowercase letters for the user name, so I needed to use "kma" (koma was taken). Thanks for your interest in Apache Kafka! -Bill On Wed, Feb 22, 2023 at 10:06 AM koma zhang wrote: > my email: komazhang0...@gmail.com > preferred

[jira] [Created] (KAFKA-14740) Missing source tag on MirrorSource metrics

Mickael Maison created KAFKA-14740: -- Summary: Missing source tag on MirrorSource metrics Key: KAFKA-14740 URL: https://issues.apache.org/jira/browse/KAFKA-14740 Project: Kafka Issue Type:

Please help to create an JIRA account for me, thanks

my email: komazhang0...@gmail.com preferred username: Koma alternate username: Kma

Re: [DISCUSS] KIP-900: KRaft kafka-storage.sh API additions to support SCRAM

Hi Luke, 1. I'm going to assume that migration from ZK to KRaft will sync the info from ZK into the metadata log. There will be no need to bootstrap SCRAM for KRaft in the migration case. I will need to test this. 2. Done! I've also added a comment to each case so people understand the change.

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

See

Re: [DISCUSS] KIP-641 An new java interface to replace 'kafka.common.MessageReader'

On 2023/02/22 10:01:29 Alexandre Dupriez wrote: > Hi Chia-Ping, > > Thanks for your answer. Apologies I should have been clearer in the > previous message. What I meant is, is there a plan to use the SPI more > broadly inside the Kafka codebase? no, there is no plan to reuse the SPI. > The

Re: [DISCUSS] KIP-900: KRaft kafka-storage.sh API additions to support SCRAM

Hi Proven, Thanks for the KIP. Some questions: 1. During ZK migrating to KRaft, should we format the KRaft controller with the SCRAM info, or it'll sync from ZK? 2. In the KIP, you provided a link to a doc from Confluent (i.e. this line: See Configuring SCRAM

Re: [DISCUSS] KIP-641 An new java interface to replace 'kafka.common.MessageReader'

Hi Chia-Ping, Thanks for your answer. Apologies I should have been clearer in the previous message. What I meant is, is there a plan to use the SPI more broadly inside the Kafka codebase? The question arises because the interface exposes a close() method which is never invoked by the

Re: [DISCUSS] KIP-641 An new java interface to replace 'kafka.common.MessageReader'

> A minor comment. The SPI is currently used exclusively for the > ConsoleProducer. However, it exposes high-level methods which hint at > it being a generic component. What is the actual scope of the SPI > inside the Kafka codebase? Is it planned to be re-used in other tools? > Or is this