Hi Kasper,
> Starting with Kafka v3.8.0, methods like logAuditMessage and isSuperUser
in AclAuthorizer were made private, which breaks our implementation.
> 1. Is this change intentional, and if so, is there a recommended way to
handle logging or superuser checks in custom authorizers?
I checked t
Hello,
We have a kafka streams service that performs a left join (KStreams)
operation by their message key. The message size is 1 KB more or less.
The left topic has around two hundred thousand (200,000) messages per
second, while the right topic has around two thousand (2000) message per
seco
Hi,
We’re upgrading from Kafka v3.7.1 to v3.9.0 and encountered issues with our
custom Kafka Authorizer that extends AclAuthorizer. Starting with Kafka v3.8.0,
methods like logAuditMessage and isSuperUser in AclAuthorizer were made
private, which breaks our implementation.
1. Is this change i
Thanks all for the response, I'm in the process of designing, so one more
question ..
We have Strimzi Kafka deployed and the strimzi schema registry internally
uses the Confluent Schema registry .. i understand this is free to use, but
not integrated with Confluent Cloud (which is ok since we don't
This was fixed in https://github.com/apache/kafka/pull/18146
On Tue, Nov 12, 2024 at 4:41 PM Thomas Thornton
wrote:
> Hi we notice data loss i.e. dropped records when running Debezium on Kafka
> Connect with Apicurio Schema Registry. Specifically, multiple times we have
> observed that a single
Dear Team,
Has anyone experienced this issue as I am also experiencing the similar
issue with 3 node clusters in isolated mode, even though the
StandardAuthorizer is enabled its still giving this error.
appuser@kafka01 secrets]$ kafka-acls --bootstrap-server
broker01.abc.net:9094 --command-config
