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

See

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

See

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

See Changes: -- [...truncated 507023 lines...] [2022-09-26T23:29:02.737Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 166 >

Re: [DISCUSS] KIP-871: Fix ByteBufferSerializer#serialize(String, ByteBuffer) compatible problem

Hello ShunKang, Thanks for filing the report. I looked at the source code and I agree it's a bug. The reason we did not get it in the past is probably just because we were inefficiently keep byte-copying and hence for almost all cases, the offset is set to 0 when serialization happens. Note that

[jira] [Created] (KAFKA-14261) Dependency Vulnerability Scan Results (Mend/WhiteSource)

VeeVee Wang created KAFKA-14261: --- Summary: Dependency Vulnerability Scan Results (Mend/WhiteSource) Key: KAFKA-14261 URL: https://issues.apache.org/jira/browse/KAFKA-14261 Project: Kafka Issue

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.3 #87

See

Re: [VOTE] 3.3.0 RC2

Thanks for the votes, everyone! Here is the best recent run of the system tests on 3.3 http://confluent-kafka-system-test-results.s3-us-west-2.amazonaws.com/3.3/2022-09-24--001.system-test-kafka-3.3--1664037736--confluentinc--3.3--b084e9068c/report.html. I'm currently re-running the failed tests

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

See Changes: -- [...truncated 508863 lines...] [2022-09-26T21:03:29.661Z] > Task :connect:api:testJar [2022-09-26T21:03:29.661Z] > Task :connect:api:testSrcJar

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Re versions: fair enough, I think it's okay to keep it as strings. Just to clarify the concern I had is that if we do want to augment it in the future, it will be harder to change a `string` field into a `struct` :P Re onAssignment: actually even with the current proposal, since we are giving the

[jira] [Resolved] (KAFKA-14207) Add a 6.10 section for KRaft

[ https://issues.apache.org/jira/browse/KAFKA-14207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jose Armando Garcia Sancio resolved KAFKA-14207. Resolution: Fixed > Add a 6.10 section for KRaft >

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Regarding the version, I would rather add this later when we have a clear use case for it. It seems to me that we are speculating here. I understand your point but I am not fully convinced by the solution at the moment. Would you agree with this? Regarding the onAssignment, I was thinking about

Re: [VOTE] 3.3.0 RC2

+1 provided that the system test results are good. Can you please post them along with the JUnit test results (these seem ok although there are some flakes)? I tested the kraft quick start with the Scala 2.13 binary and ran the tests on the source release. I noticed a non-blocker issue with the

Re: [VOTE] 3.3.0 RC2

+1 (non-binding). I used the staged binaries (Scala 2.13) and Maven artifacts and ran my tests. All seems to work fine. Thanks for running the release. Jakub On Wed, Sep 21, 2022 at 1:17 AM David Arthur wrote: > Hello Kafka users, developers and client-developers, > > This is the second

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Regarding the version, what I was thinking is that in the HB request, for "serverAssignor" field, instead of just having it as a single string field, maybe we could consider also making it a structure that includes: name, minimumVersion, maximumVersion. Where the minimumVersion/maximumVersion

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.3 #86

See

Re: [VOTE] 3.3.0 RC2

Hi Jose and David, Thanks for running the release! I did the following verification steps: I performed the following validations: 1. Verified all checksums and signatures. 2. Built from source and ran unit tests. 3. Ran the first quickstart steps 1. Zookeeper quick start

Re: [VOTE] 3.3.0 RC2

Thanks for running the release, José and David. I performed the following validations: * Verified all checksums and signatures. * Built from source and ran unit tests. * Ran the first quickstart steps for both ZK and KRaft. * Spotchecked the Javadocs. I have also noticed that the doc is

Re: [VOTE] 3.3.0 RC2

Thanks for running this, David! I've verified the signatures, looked at the docs, and run the quickstart (ZK and KRaft). I also ran the unit tests, as well as all the tests for Streams locally. The docs look a little malformed (the "collapse/expand" button floats over the text, the collapsed

Re: [kafka-clients] Re: [VOTE] 3.3.0 RC2

Happy Monday, everyone! I've uploaded the 3.3 docs to the website to make that part of the release validation easier https://kafka.apache.org/33/documentation.html These docs are not referenced by the top level docs page, so they can only be accessed directly via the "33" url above. I'd like to

Re: [DISCUSS] KIP-793: Sink Connectors: Support topic-mutating SMTs for async connectors (preCommit users)

Hi Randall, Thanks for reviewing the KIP! > That latter logic can get quite ugly. I'm not sure I quite understand why it would be "easier" for connector developers to account for implementing two different overloaded `put` methods (assuming that they want to use this new feature) versus using a

[GitHub] [kafka-site] mumrah merged pull request #445: Pre-release of Kafka 3.3 documentation

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

Re: PR for CVE-2022-34917

Hi Swathi, In this case the PR reviews happened on a private repo because the CVE wasn't public at that time. On the 3.3 branches you can look at/cherry-pick commits 015d7aede6cbd350d56d75006930dd2bf89a4a5a and b2b928338c7226b41a73786df27a2127eaa32ab2. Kind regards, Tom On Mon, 26 Sept 2022

[GitHub] [kafka-site] mumrah commented on pull request #445: Pre-release of Kafka 3.3 documentation

mumrah commented on PR #445: URL: https://github.com/apache/kafka-site/pull/445#issuecomment-1258126700 @ijuma yea, I just did: * untar * mv site-docs 33 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: PR for CVE-2022-34917

https://issues.apache.org/jira/browse/KAFKA-14063?focusedCommentId=17608137=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17608137 On Mon, Sep 26, 2022 at 7:42 PM Swathi Mocharla wrote: > > Hi, > CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-34917 > Could you please

[GitHub] [kafka-site] mumrah opened a new pull request, #445: Pre-release of Kafka 3.3 documentation

mumrah opened a new pull request, #445: URL: https://github.com/apache/kafka-site/pull/445 This adds the documentation for 3.3 generated at https://github.com/apache/kafka/commit/6174f95d61c54fb228fc23e5111e2941f3947cad. This PR does _not_ include the updated reference in the top-level

PR for CVE-2022-34917

Hi, CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-34917 Could you please help with the PR that fixed this vulnerability? We are looking to apply the patch that fixes this and we are unable to find it. Thanks, Swathi

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi Guozhang, Regarding the version, my understanding is that the version would be either the client software version or the request version, is this correct? If so, we could indeed pass this information down to the assignor via the interface. One way would be to pass a "server context" to the

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.3 #85

See

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

See