Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.9 #116

See

Re: [DISCUSS] KIP-1030: Change constraints and default values for various configurations

About replication.factor >= min.insync.replicas change, you should look at https://issues.apache.org/jira/browse/KAFKA-4680 . That JIRA talks about some of the complexities of detecting it. For example, what if a topic has replication factor 1, but someone changes the broker-level min.insync.rep

Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool to support new consumer group

hi PoAn `isClassic` is good to me :) Best, Chia-Ping PoAn Yang 於 2024年11月23日 週六 下午12:35寫道： > Hi Chia-Ping / David, > > Thanks for the great suggestion. > > How about using “isClassic”? > The term like “isLegacy” may be equivocal in the future. > For example, if we have a newer version of consu

Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool to support new consumer group

Hi Chia-Ping / David, Thanks for the great suggestion. How about using “isClassic”? The term like “isLegacy” may be equivocal in the future. For example, if we have a newer version of consumer / share consumer, the meaning will be different for different cases. If we use “isClassic”, for MemberD

[jira] [Created] (KAFKA-18074) Add kafka client compatibility matrix

Chia-Ping Tsai created KAFKA-18074: -- Summary: Add kafka client compatibility matrix Key: KAFKA-18074 URL: https://issues.apache.org/jira/browse/KAFKA-18074 Project: Kafka Issue Type: Improve

Jenkins build is still unstable: Kafka » Kafka PowerPC Daily » test-powerpc #126

See

[jira] [Created] (KAFKA-18073) Data loss when Kafka Connect retriable exception raised

Tom Thornton created KAFKA-18073: Summary: Data loss when Kafka Connect retriable exception raised Key: KAFKA-18073 URL: https://issues.apache.org/jira/browse/KAFKA-18073 Project: Kafka Issue

[jira] [Resolved] (KAFKA-18051) Disallow creating ACLs with principals that do not contain a colon

[ https://issues.apache.org/jira/browse/KAFKA-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-18051. -- Resolution: Fixed > Disallow creating ACLs with principals that do not contain a colon > -

[jira] [Resolved] (KAFKA-18072) Data corruption in netty version to 4.1.111.Final

[ https://issues.apache.org/jira/browse/KAFKA-18072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Thornton resolved KAFKA-18072. -- Resolution: Fixed This was fixed by https://github.com/apache/kafka/pull/17860 > Data corrup

[jira] [Created] (KAFKA-18072) Data corruption in netty version to 4.1.112.Final

Tom Thornton created KAFKA-18072: Summary: Data corruption in netty version to 4.1.112.Final Key: KAFKA-18072 URL: https://issues.apache.org/jira/browse/KAFKA-18072 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

hi, A1. Personally, I prefer the suggestion: require.auto.generated.topic.names. If everyone agrees, I will update the KIP accordingly. MJS-1. Sophie, I reviewed the ticket and the sub-tasks, and everything seems clear to me. I must say that I sometimes felt confused with the constructors, but no

Re: [DISCUSS] KIP-1115: Bazel Builds

Also worth mentioning - Develocity does have support for caching and build analysis with Bazel - https://gradle.com/gradle-enterprise-solutions/bazel-build-system/ I don't know about Gradle's partnership with ASF, Are they requiring Kafka to use Gradle to get the cache and analysis UI? On Fri, Nov

[jira] [Resolved] (KAFKA-18000) Fix flaky ReplicaManagerTest#testSuccessfulBuildRemoteLogAuxStateMetrics

[ https://issues.apache.org/jira/browse/KAFKA-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-18000. Fix Version/s: 4.0.0 Resolution: Fixed > Fix flaky ReplicaManagerTest#testSuccessfu

Re: [DISCUSS] KIP-1115: Bazel Builds

On Fri, Nov 22, 2024 at 10:47 AM David Arthur wrote: > > Thanks for the KIP, Vince and Farid! > > A few comments on the KIP > > DA1: The motivation mentioned historical build times in Apache Kafka, but > we should really just consider the current situation. I would like to see > the motivation/bac

Re: [DISCUSS] KIP-1115: Bazel Builds

Thanks for the KIP, Vince and Farid! A few comments on the KIP DA1: The motivation mentioned historical build times in Apache Kafka, but we should really just consider the current situation. I would like to see the motivation/background make a clearer distinction between trunk builds (no caching)

Re: [DISCUSS] KIP-1115: Bazel Builds

Bringing fzaka...@confluent.io into the discussion. On Fri, Nov 22, 2024 at 10:01 AM Viktor Somogyi-Vass wrote: > Hi Vincent > > I would also like to say that I'm not an expert in Bazel either. Generally > I think it's good to reduce build and test times in every infra. While > reading up on Baz

Re: [DISCUSS] KIP-1115: Bazel Builds

Hi! I'm one of the co-authors of the KIP. Let me answer a few questions (the thread is a bit long so I won't opt for inline). * Many of the comments touch on the aspect that having multiple BUILD files looks like to be higher cognitive requirement than what is currently required by Gradle which s

Re: [DISCUSS] KIP-1115: Bazel Builds

On Fri, Nov 22, 2024 at 10:01 AM Viktor Somogyi-Vass wrote: > Hi Vincent > > I would also like to say that I'm not an expert in Bazel either. Generally > I think it's good to reduce build and test times in every infra. While > reading up on Bazel, it seems like it's most useful in monolithic code

Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool to support new consumer group

hi DJ > My goal was to have a way to tell the user that his (new) consumer group may have non-upgraded members yet. I wonder if we could use a boolean to signal this, e.g. isLegacy. Then, in the CLI we could have a column which is only displayed when they are non upgraded members. What do you thin

Re: [DISCUSS] KIP-1115: Bazel Builds

Hi Vincent I would also like to say that I'm not an expert in Bazel either. Generally I think it's good to reduce build and test times in every infra. While reading up on Bazel, it seems like it's most useful in monolithic code bases, such as Confluent as you mentioned in the KIP (so it's not a co

Re: [DISCUSS] KIP-1115: Bazel Builds

Thanks for the KIP Vince and Farid! Glad to see Bazel being considered for Kafka and really impressive work on the demo repository! From the benchmarks, I'd imagine the build would only get faster once BUILD.bazel files don't glob the entire source/test set for a module but are more fine grain

Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool to support new consumer group

Hi both, Ah, I understand what you mean now. You're saying that we have two protocol fields. One at the group level and one at the member level (the new one). The two fields are actually two different things. The former is the name of the embedded protocol used in the classic protocol whereas the

[jira] [Created] (KAFKA-18071) Avoid unneeded background event to refresh regex if no subscription pattern in use

Lianet Magrans created KAFKA-18071: -- Summary: Avoid unneeded background event to refresh regex if no subscription pattern in use Key: KAFKA-18071 URL: https://issues.apache.org/jira/browse/KAFKA-18071

Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool to support new consumer group

Hi Chia-Ping / David, Thanks for the review and suggestions. >> I don't fully follow your comment so please excuse me if I say something >> wrong. I think Chia-Ping wants to say: originally, the default protocol in classic group is “consumer”. After we have a new consumer group, the protocol of

[jira] [Resolved] (KAFKA-18059) kafka-metadata-quorum.sh add-controller subcommand can't recognize argument --config

[ https://issues.apache.org/jira/browse/KAFKA-18059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18059. Fix Version/s: 4.0.0 Resolution: Fixed > kafka-metadata-quorum.sh add-controller su

Re: [DISCUSS] KIP-1098: Reverse Checkpointing in MirrorMaker

Hey Daniel, SVV3. Thanks for the explanation. I don't think there is any preference in terms of null values vs defaults. Regarding the TopicFilter, I still have some concerns as "shouldReplicateTopic" could be a little bit misleading in terms of wording. Just modifying my SVV4 point, have you thou

[jira] [Created] (KAFKA-18070) Update kafka-metadata-quorum.sh output in docs to match post-KIP-853 appearance

Colin McCabe created KAFKA-18070: Summary: Update kafka-metadata-quorum.sh output in docs to match post-KIP-853 appearance Key: KAFKA-18070 URL: https://issues.apache.org/jira/browse/KAFKA-18070 Proje

[jira] [Resolved] (KAFKA-18065) be helpful when throwing ConcurrentModificationException out of consumers

[ https://issues.apache.org/jira/browse/KAFKA-18065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18065. Resolution: Won't Fix [~peterxcli] thanks for your inforamtion > be helpful when throwing

Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool to support new consumer group

Hi Chia, > > LM4: I agree it’s better to use a type like GroupProtocol enum, but I would like to align the format with kafka-groups.sh. How about we use another Jira to add “SHARE” to GroupProtocol and change return type of ModernGroup#protocolType? My understanding is that `GroupProtocol` is use

Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool to support new consumer group

hi DJ > How about we use another Jira to add “SHARE” to GroupProtocol and change return type of ModernGroup#protocolType? This is not my comment ... sorry for the incorrect quote :( > A member in a classic group should report "classic". I completely agree. However, in this case, ClassicGroupDes

[jira] [Created] (KAFKA-18069) Out of order output from windowed aggregations

Rhishikesh Joshi created KAFKA-18069: Summary: Out of order output from windowed aggregations Key: KAFKA-18069 URL: https://issues.apache.org/jira/browse/KAFKA-18069 Project: Kafka Issue

[jira] [Created] (KAFKA-18068) Fixing typo in ProducerConfig

Robert V created KAFKA-18068: Summary: Fixing typo in ProducerConfig Key: KAFKA-18068 URL: https://issues.apache.org/jira/browse/KAFKA-18068 Project: Kafka Issue Type: Bug Reporter: R

[jira] [Resolved] (KAFKA-17964) TransactionsTest.testSendOffsetsWithGroupId fails with CONSUMER group protocol

[ https://issues.apache.org/jira/browse/KAFKA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17964. Fix Version/s: (was: 4.0.0) Resolution: Won't Fix the test is removed by KAFKA-

[jira] [Resolved] (KAFKA-17961) TransactionsBounceTest.testWithGroupId fails with CONSUMER group protocol

[ https://issues.apache.org/jira/browse/KAFKA-17961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17961. Fix Version/s: (was: 4.0.0) Resolution: Won't Fix the test is removed by KAFKA-

[jira] [Resolved] (KAFKA-12690) Remove deprecated Producer#sendOffsetsToTransaction

[ https://issues.apache.org/jira/browse/KAFKA-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-12690. Resolution: Fixed > Remove deprecated Producer#sendOffsetsToTransaction >

Re: [DISCUSS] KIP-1099: Extend kafka-consumer-groups command line tool to support new consumer group

hi PoAn > LM4: I agree it’s better to use a type like GroupProtocol enum, but I would like to align the format with kafka-groups.sh. How about we use another Jira to add “SHARE” to GroupProtocol and change return type of ModernGroup#protocolType? MemberDescription is also used by ClassicGroupDesc

[jira] [Created] (KAFKA-18067) Kafka Streams can leak Producer client under EOS

A. Sophie Blee-Goldman created KAFKA-18067: -- Summary: Kafka Streams can leak Producer client under EOS Key: KAFKA-18067 URL: https://issues.apache.org/jira/browse/KAFKA-18067 Project: Kafka