Re: [VOTE] 3.8.1 RC1

Hi Josep, +1(non-binding) I did the following - Built from different JDK (8, 11, 17, 21) in Docker image - Ran all the unit test and integration test in container Best regards, Jiunn-Yang > TengYao Chi 於 2024年10月26日 凌晨12:22 寫道： > > Hi Josep, > > Thanks for handling the release of the 3.8.1 R

Re: [VOTE] 3.9.0 RC2

Colin I have presented four reasons, I'll list them again below. Please let me know which ones there isn't already enough information on the thread already. - The behavior is new. - The behavior is undocumented. - The behavior is bad API design. - The behavior does not really save bytes *in pract

Kafka wire protocol and Wireshark capture don't seem to align.

Hello, I set-up a simple Java client to publish a sample message to Kafka broker. I can see API Versions request v3 and response messages. I am able to map all the bytes as described here ( https://kafka.apache.org/protocol.html#The_Messages_ApiVersions) for API Versions request and response except

[jira] [Created] (KAFKA-17882) improve the document about "default value" of tagged structure field

Chia-Ping Tsai created KAFKA-17882: -- Summary: improve the document about "default value" of tagged structure field Key: KAFKA-17882 URL: https://issues.apache.org/jira/browse/KAFKA-17882 Project: Kaf

[DISCUSS] KIP-1100: Consider renaming org.apache.kafka.server:type=AssignmentsManager

Hello everyone, I would like to start a discussion about KIP-1100 In this KIP, we plan to update the `AssignmentsManager` metric name from `org.apache.kafka.server

Re: [VOTE] 3.9.0 RC5

hi Anton Thanks for sharing your insights on Kafka serialization—it’s really cool and interesting to me. Additionally, you inspired me to file a JIRA issue (KAFKA-17882) to improve the documentation. The most important aspect of Kafka is compatibility, and the undocumented behavior has been in

Re: Kafka wire protocol and Wireshark capture don't seem to align.

hi Chain > ? - 1 byte value 0x3c This magic byte represents the size of the following 'Array of API keys.' We need to know the size of the array to determine how many elements must be read from the network. Here's a snippet demonstrating how the size is used. ``` int arrayLength = _readable.rea

Re: [DISCUSS] KIP-1100: Consider renaming org.apache.kafka.server:type=AssignmentsManager

hi Jiunn-Yang Thanks for this KIP. *Q0:* Should we add "deprecation" to the MBean description instead of logging it? *Q1:* To allow users to migrate to the new metrics now, should we add the metric kafka.server:type=AssignmentsManager at the same time? Best, Chia-Ping 黃竣陽 於 2024年10月28日 週一 上

Re: [DISCUSS] KIP-1100: Consider renaming org.apache.kafka.server:type=AssignmentsManager

Hi Chia-Ping Thanks for your comments, > *Q0:* Should we add "deprecation" to the MBean description instead of logging > it? > *Q1:* To allow users to migrate to the new metrics now, should we add the > metric kafka.server:type=AssignmentsManager at the same time? It seems to deprecate old met

Re: [VOTE] 3.8.1 RC1

Hi Josep, Thanks for the RC. I did the following - checked the checksums and signatures - ran upgrade from v3.7.1 to v3.8.1 - ran quickstart with the 2.13 binaries - reviewed doc update PR. +1 (binding) from me. Thanks. Luke On Mon, Oct 28, 2024 at 8:16 AM 黃竣陽 wrote: > Hi Josep, > > +1(non-b

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

Hi Frank, Thanks for the KIP! Since we’re updating kafka-consumer-groups to add epoch information from the new protocol, I wonder if it’s feasible to also add leader epoch information when printing --offsets. leaderEpoch was added in KIP-320 and we neglected to update kafka-consumer-groups at

Re: [PR] [Docs] Update site for 3.8.1 [kafka-site]

showuon commented on code in PR #635: URL: https://github.com/apache/kafka-site/pull/635#discussion_r1818330008 ## 38/js/templateData.js: ## @@ -19,6 +19,6 @@ limitations under the License. var context={ "version": "38", "dotVersion": "3.8", -"fullDotVersion": "3.

Re: [VOTE] 3.9.0 RC5

-1, refer to comments on the RC 2 thread. Den sön 27 okt. 2024 kl 02:51 skrev Colin McCabe : > This is the RC5 candidate for the release of Apache Kafka 3.9.0. > > - This is a major release, the final one in the 3.x line. (There may of > course be other minor releases in this line, such as 3.9.1.

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

See

[jira] [Resolved] (KAFKA-17881) Apply the minJavaVersion to test code

[ https://issues.apache.org/jira/browse/KAFKA-17881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17881. Fix Version/s: 4.0.0 Resolution: Fixed > Apply the minJavaVersion to test code > --

[jira] [Created] (KAFKA-17884) SLF4J error when running Kafka in IDEA

Xiang Zhang created KAFKA-17884: --- Summary: SLF4J error when running Kafka in IDEA Key: KAFKA-17884 URL: https://issues.apache.org/jira/browse/KAFKA-17884 Project: Kafka Issue Type: Wish Aff

[jira] [Created] (KAFKA-17881) Apply the minJavaVersion to test code

Chia-Ping Tsai created KAFKA-17881: -- Summary: Apply the minJavaVersion to test code Key: KAFKA-17881 URL: https://issues.apache.org/jira/browse/KAFKA-17881 Project: Kafka Issue Type: Bug

Re: Kafka wire protocol and Wireshark capture don't seem to align.

Yes, I realised that too. In fact, if the response version is <3, then the size will be INT32. However, how would Wireshark know what version of response was sent? On Sun, Oct 27, 2024 at 10:18 PM Chia-Ping Tsai wrote: > hi Chain > > > ? - 1 byte value 0x3c > > This magic byte represents the siz

Re: Kafka wire protocol and Wireshark capture don't seem to align.

> However, how would Wireshark know what version of response was sent? The version matches the ApiVersionsRequest that was sent. Chain Head 於 2024年10月28日 週一 上午2:02寫道： > Yes, I realised that too. In fact, if the response version is <3, then the > size will be INT32. However, how would Wireshark

Re: [VOTE] KIP-891: Running multiple versions of Connector plugins

Thanks everyone, Have moved the status of the KIP to Accepted and updated the docs appropriately. Regards Snehashis On Wed, Oct 23, 2024 at 9:27 PM Mickael Maison wrote: > Hi, > > +1 (binding), thanks for the KIP! > > Mickael > > On Tue, Oct 22, 2024 at 10:35 PM Greg Harris > wrote: > > > > H

[jira] [Resolved] (KAFKA-17879) test_performance_services.py should use DEV version to run kafka service

[ https://issues.apache.org/jira/browse/KAFKA-17879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17879. Fix Version/s: 4.0.0 Resolution: Fixed > test_performance_services.py should use DE

[jira] [Reopened] (KAFKA-12894) KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)

[ https://issues.apache.org/jira/browse/KAFKA-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai reopened KAFKA-12894: re-open to make sure e2e get passed > KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecat

[jira] [Created] (KAFKA-17883) Fix jvm error caused by UseParNewGC when running old kafka client in e2e

Chia-Ping Tsai created KAFKA-17883: -- Summary: Fix jvm error caused by UseParNewGC when running old kafka client in e2e Key: KAFKA-17883 URL: https://issues.apache.org/jira/browse/KAFKA-17883 Project: