Hi Miguel,
Kafka v3.1.0 has already code freezed, and is dealing with some blocker
issues. It should be released soon.
For this feature status in v3.0.0, I think Matthias knows it the most.
As far as I know, it was ready for v3.0.0 originally, but there's a
regression bug found(KAFKA-13216
Hello All,
We are currently using Kafka Connect and a JMS sink connector (custom
implementation) to send messages from a Kafka topic to an ActiveMQ queue,
messages are produced in a single Kafka topic without any key (round-robin
partitioning).
While using the connector we observed that, for each
Hi, I have a 6 node cluster with Kafka 3.0.0 with 5 nodes running in dual mode
(controller and broker) using instructions from here:
https://github.com/apache/kafka/blob/3.0/config/kraft/README.md. They are
running fine.
I set up the 6th one as just a broker to experiment. It fails to startup w
Hi all,
Here's the comments for CVE-2021-44228 vulnerability *from SLF4J project*.
REF: http://slf4j.org/log4shell.html
I think it's a analysis that worth reading. Most importantly, it has
comments about log4j 1.x versions, which is currently Kafka used.
I quote some sentences here for your refer
Hi Matthias
Do you know when the 3.1 version is going to be released?
I noticed the JoinWindows class has a boolean property called
enableSpuriousResultFix
If I extend the class the set that flag to true will it eliminate spurious
messages in kafka streams 3.0.0 ?
thanks
- Miguel
On Mon, Dec
Thanks guys!
On Mon, Dec 13, 2021 at 7:43 AM Brian Rickabaugh
wrote:
> I strongly recommend that the Kafka community publish a statement on this
> vulnerability.
>
> This Log4J exploit is getting a lot of publicity in my organization and a
> page to point our security team to would be very hel
Hi,
for me and my team, the following problem already took many resources from us
and after one year of struggeling we couldn't solve it yet.
In one of our spring based applications we use Kafka State Stores with the
following initialization.
@Bean
public KafkaStreams myStuffMessagesStream(@Qu
Hi,
for me and my team, the following problem already took many resources from us
and after one year of struggeling we couldn’t solve it yet.
In one of our spring based applications we use Kafka State Stores with the
following initialization.
@Bean
public KafkaStreams myStuffMessagesStream(@
I strongly recommend that the Kafka community publish a statement on this
vulnerability.
This Log4J exploit is getting a lot of publicity in my organization and a
page to point our security team to would be very helpful.
Brian
Quoting Luke Chen :
Due to this vulnerability is quite critical a
I strongly recommend that the Kafka community publish a statement on this
vulnerability.
This Log4J exploit is getting a lot of publicity in my organization and a
page to point our security team to would be very helpful.
Brian
Quoting Luke Chen :
Due to this vulnerability is quite critical a
Hi Jigar,
As Liam mentioned, those are necessary consumer initialization processes.
So, I don't think you can speed it up by altering some timeouts/interval
properties.
Is there any reason why you need to care about the initial delay?
If, like you said, the delay won't happen later on, I think the
Hello ,
Answering your first mail, indeed I am using consumer groups using group.id
, I must have missed to add it in mentioned properties
Also, thank you for information regarding the internal processes working
behind creating a KafkaConsumer.
I agree that following steps do add latency during ini
Due to this vulnerability is quite critical and "popular" in these days,
should *Kafka have an official announcement in our security cve list page
or somewhere*? (i.e. https://kafka.apache.org/cve-list)
So far, my assessment is that, Kafka is not using log4j 2.x versions, so
the risk is lower.
Kaf
13 matches
Mail list logo