>
> if we are just creating a global state store (GlobalKTable
> for instance) from a topic, then that is what you are calling as
> global-only topology.
Exactly. If there is no KStream or KTable in your Streams topology,
just a GlobalKTable, then that would be a "global-only" topology
On Mon,
Hi Pushkar,
I'd recommend always keeping Streams and the Clients at the
same version, since we build, test, and release them
together. FWIW, I think there were some bugfixes for the
clients in 2.5.1 anyway.
Thanks,
-John
On Mon, 2020-09-14 at 20:08 +0530, Pushkar Deole wrote:
> Sophie, one more
Sophie, one more question: will just upgrading kafka-streams jar to 2.5.1
will work or we need to other jars also to be upgraded to 2.5.1 e.g.
kafka-clients etc. ?
On Mon, Sep 14, 2020 at 7:16 PM Pushkar Deole wrote:
> Thanks Sophie... if we are just creating a global state store
>
Thanks Sophie... if we are just creating a global state store (GlobalKTable
for instance) from a topic, then that is what you are calling as
global-only topology. In our application that is what we are doing and
there is no source topic for the stream to process data from, i mean there
is however
You should upgrade to 2.5.1, it contains a fix for this.
Technically the "fix" is just to automatically set the num.stream.threads
to 0
when a global-only topology is detected, so setting this manually would
accomplish the same thing. But the fix also includes a tweak of the
KafkaStreams state
Hi All,
I upgraded from Kafka streams 2.4 to 2.5.0 and one of the applications
suddenly stopped working with the error message:
Exception in thread
"DsiApplication-0fcde033-dab2-431c-9d82-76e85fcb4c91-StreamThread-1"
java.lang.IllegalStateException: Consumer is not subscribed to any topics
or
