Hi Bruno,
+1 (non binding)
- Checked documentation and blog post
- Ran some client tests using the staged artifacts
- Verified the signing key and sha512 sum
- Built from source
- Ran unit and integration tests
Thanks
Fede
On Thu, May 12, 2022 at 12:03 PM Bruno Cadonna wrote:
>
> Hi all,
>
> P
gpg: Good signature from "David Arthur (CODE SIGNING KEY)
" [unknown]
/tmp/tmp.lRpAY/kafka-3.2.1-src.tgz.sha512: OK
Build using Gradle 7.3.3, Java 11 and Scala 2.13.8
BUILD SUCCESSFUL in 5m 34s
Unit and integration tests:
BUILD SUCCESSFUL in 37m 47s
I also used Scala 2.13 binaries and staged Ma
Hi, I did the following to validate the release:
- Checksums and signatures ok
- Build from source ok
- Unit and integration tests ok
- Quickstart in both ZK and KRaft modes ok
- Test Java app with staging Maven artifacts ok
+1 (non binding)
Thanks
Fede
On Sun, Oct 2, 2022 at 7:47 PM José Arman
Hi, I did the following to validate the release:
- Checksums and signatures ok
- Build from source using Java 17 and Scala 2.13 ok
- Unit and integration tests ok
- Quickstart in both ZK and KRaft modes ok
- Test app with staging Maven artifacts ok
Documentation still has 3.3.1 version references
+1 (non binding)
- Ran the unit and integration test suites with Java 17 and Scala 2.13
- Ran a series of basic examples and client configurations
- Spot checked the docs and Javadocs
Thanks
Fede
On Fri, Feb 3, 2023 at 5:29 PM Jakub Scholz wrote:
>
> +1 (non-binding). I run my tests with the st
Hi Luke, thanks for running the release.
Looks like the Maven artifacts are not in staging:
https://repository.apache.org/content/groups/staging/org/apache/kafka/kafka-clients/3.4.1/
Documentation still has 3.4.0, instead of 3.4.1 (not sure if this will
be aligned later):
https://kafka.apache.org
Hi Luke,
- Source signature and checksum
- Build from source with Java 17 and Scala 2.13
- Full unit and integration test suite
- Java app with staging Maven artifacts
+1 (non binding)
Thanks
Fede
PS: Links still point to RC0, but I checked and RC1 artifacts are
there, including Maven. The only
Hi Luke,
- Checked signature, checksum, libs, and license file
- Build from source with Java 17 and Scala 2.13
- Ran full unit and integration test suites
- Ran Java app with staging Maven artifacts against ZK and KRaft
multi-node clusters
+1 (non binding)
Thanks
Fede
On Fri, May 26, 2023 at 1
Hi Mickael, I did the following checks:
- Signature, checksum, licenses
- Build from source with Java 17 and Scala 2.13
- Full unit and integration test suites
- Java app with staging Maven artifacts and multi-node cluster
LGTM, apart from the already mentioned "classgraph" license that can be re
Hi Divij, thanks for running the release.
I found a couple of issues with licenses. We include
plexus-utils-3.3.1, but the LICENSE file has plexus-utils-3.3.0. The
other issue is that we have classgraph-4.8.138, but we don't include
this library for a few releases (this is non blocking but it woul
Hi Divij, I did the following checks:
- Checked signature, checksum, licenses
- Spot checked documentation and javadoc
- Built from source with Java 17 and Scala 2.13
- Ran full unit and integration test suites
- Ran test Java app using staging Maven artifacts
+1 (non binding)
Cheers
Fede
On Mo
Hi Satish, I did the following to verify the release:
- Verified signature and checksum
- Built from source with Java 17 and Scala 2.13
- Ran all unit and integration tests
- Spot checked release notes and documentation
- Ran a custom client using staging artifacts on a 3-nodes cluster
- Tested ti
Hi Satish, I did the following to verify the release:
- Built from source with Java 17 and Scala 2.13
- Ran all unit and integration tests
- Spot checked documentation
- Ran custom client applications using staging artifacts on a 3-nodes cluster
- Tested tiered storage with one of the available RS
Hi Jakub, as you say, this was supposed to work according to
documentation and KIP-778. Instead, the "unsafe" override is not yet
implemented. For this reason, I logged a bug and proposed a
documentation fix.
https://issues.apache.org/jira/browse/KAFKA-15537
Thanks for raising.
Br
Fede
On 2023/
Hi Luke,
- Compiled from source (Java 17 and Scala 2.13)
- Ran unit and integration tests
- Ran custom client apps using staging artifacts
+1 (non binding)
Thanks
Fede
On Wed, Nov 22, 2023 at 2:44 PM Josep Prat wrote:
>
> Hi Luke,
>
> Thanks for running the release.
> I did the following:
> -
Hi Mickael,
- Build from source (Java 17, Scala 2.13)
- Run unit and integration tests
- Run custom client apps using staging artifacts
+1 (non binding)
Thanks
Fede
On Sun, Nov 26, 2023 at 11:34 AM Jakub Scholz wrote:
>
> +1 non-binding. I used the staged Scala 2.13 artifacts and the staged
Hi David, I've tested the RC4 and this is what I've done:
- Used the binaries to create a cluster and run clients from exampled module
- Tested the upgrade issue we found in KAFKA-18979
- Tested the dynamic quorum feature (both scale up and down)
- Tested group.protocol=consumer with a simple Java
Yes, I was about to post the same. You can also directly check Jetty
version on Kafka 4.0.0 tag:
https://github.com/apache/kafka/blob/4.0.0/gradle/dependencies.gradle#L71
On Mon, May 19, 2025 at 4:57 PM Steven Schlansker
wrote:
>
>
> > On May 16, 2025, at 12:04 AM, Sahil Sharma D
> > wrote:
> >
Hello, to unsubscribe you have to send an email to
users-unsubscr...@kafka.apache.org.
On Wed, May 21, 2025 at 4:42 PM Владимир Бухтояров
wrote:
>
>
>
>
> Best regards,
> Bukhtoyarov Vladimir,
> Senior Java developer at vk.com
> https://github.com/vladimir-bukhtoyarov
> https://t.me/Vladimir_Bukh
Hi Prateek, I'm not sure how you are testing this. A Kafka Connect
cluster in distributed mode uses the group management protocol to
coordinate (distribute tasks across workers). This is set to
"sessioned" by default, which aims to minimize task movements during
rebalancing.
On Mon, Jun 16, 2025 a
Hi Prateek.
In a Kafka Connect cluster, the advertised address represents the
identity of the worker node. Connectors and tasks are scheduled to the
individual worker nodes based on their identity.
If you use a Kubernetes Deployment, when you roll the cluster, new
Pods with new IPs will be be cre
Yeah, it seems we forgot to update MetadataVersion class. All 4.1
versions are listed after this comment in trunk:
//
// NOTE: MetadataVersions after this point are unstable and may be changed.
// If users attempt to use an unstable MetadataVersion, they will
get an error.
// Pleas
cc users
-- Forwarded message -
From: Federico Valeri
Date: Mon, Jul 14, 2025 at 2:09 PM
Subject: MX4j support
To:
Hello devs, Kafka has support for MX4j, that can be used to expose JMX
beans over HTTP.
https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka
23 matches
Mail list logo