I'll give you two answers here: theoretical and practical.
First up, theoretically there is unfortunately no way to work around this
issue, even if you restrict your access to the KafkaStreams#store API to
the thread that created the KafkaStreams. This is because we currently have
write locking on
, 2023 5:52:02 PM
To: users@kafka.apache.org
Subject: Re: Is the KafkaStreams#store() method thread-safe?
Hi Sophie, thank you so much for sharing that. It all makes sense to me.
Unfortunately my application uses REPLACE_THREAD, so it seems like I need a
workaround for this until this
Hi Sophie, thank you so much for sharing that. It all makes sense to me.
Unfortunately my application uses REPLACE_THREAD, so it seems like I need a
workaround for this until this thread unsafeness is removed. As I raised in my
first email, would sharing only the ReadOnlyWindowStore instance wit
Hey Kohei,
Good question -- I don't think there's exactly a short answer to this
seemingly simple question so bear with me for a second.
My understanding is that KafkaStreams#store is very much intended to be
thread-safe, and would have been back when it was first added a long time
ago, and the j
Hello, I have Kafka Streams questions related to thread safety.
In my Kafka Streams application, I have 2 threads below:
* Thread A: this creates a Topology object including state stores and
everything and then eventually calls the constructor of the KafkaStreams class
and the start() method.