Hello.
I’m having a problem with Kafka protocol API.
Requests:
DescribeLogDirs Request (Version: 0) => [topics]
topics => topic [partitions]
topic => STRING
partitions => INT32
My request contains `[{topic: “blah”, partitions: [0,1,2,3,4,5,6,7,8,9]}]`, but
the result
Responses:
Hi Ashok,
Kafka 2.7.1 was built from the 2.7.1 tag [1] and looking at the
dependencies in that version [2], it should have shipped with 1.2.17.
You can verify this by looking for the log4j jar in your installation.
Because of the security vulnerabilities you mention, Kafka switched to
reload4j in
Hello Kay,
What you describe is "by design" -- unfortunately.
The problem is, that when we build the `Topology` we don't know the
partition count of the input topics, and thus, StreamsBuilder cannot
insert a repartition topic for this case (we always assume that the
partition count is the
Thanks for reaching out Yang. You should be all set.
-Matthias
On 5/16/24 7:40 AM, Yang Fan wrote:
Dear Apache Kafka Team,
I hope this email finds you well. My name is Fan Yang, JIRA ID is fanyan, I
kindly request to be added to the contributors list for Apache Kafka. Being
part of this
Dear Apache Kafka Team,
I hope this email finds you well. My name is Fan Yang, JIRA ID is fanyan, I
kindly request to be added to the contributors list for Apache Kafka. Being
part of this list would allow me to be assigned to JIRA tickets and work on
them.
Thank you for considering my
Hi,
I am having a bit of a problem here. It is a bit of an unusual use case. I am
running a single node Kafka server and
noticed that some messages I send are not passed through Kafka. They are
silently lost. The topic is created but no
data. Other topics on the same server work just fine.
Hello Kafka Team,
Request your help...
We are using Apache Kafka kafka_2.13-2.7.1 & installed on a server.
I understand it uses log4j java for logger purposes.
But we don't know, what is the log4j version it is using?
Recently we came to know that log4j_1.2.17 has some security issues, how to
Hi,
we have a Kafka streams application which merges (merge, groupByKey,
aggretgate) a few topics into one topic. The application is stateful, of
course. There are currently six instances of the application running in
parallel.
We had an issue where one new Topic for aggregation did have