More than one tumbling window
I am trying to understand whether I can achieve the following behavior with Kafka Streams, with grace configuration or in any other way:
Kafka Stream Transform – get data on demand and cache, lazy
What (if any) would be the best approach for Kafka Streams to build a table/stream fetching the data lazily when the key we asking for is not found there?
Provide a stable name for Kafka Streams internal changelog topic
Our team is using Kafka Streams version 3.6.0
. We are trying to run a Kafka Streams topology over some externally managed brokers. I’m getting the following error when the Kafka Streams application tries to create its internal changelog topic.
Why the assignment generated by Kafka Streams TaskAssignor needs a followup probing rebalance?
My application is Kakfa streams 3.4.1 for a streaming processing, and the topology is simply one input topic and 2 stateful processing nodes and a sink.
Why the generated assignment needs a followup probing rebalance?
My application is Kakfa streams 3.4.1 for a streaming processing, and the topology is simply one input topic and 2 stateful processing nodes and a sink.
Punctuator does not see changes made to Kafka Streams State Store
We have a Kafka Streams service that uses a KeyValueStore
to cache some data. While processing data it puts data into the state store and sometime it deletes data from the state store. That state store is also accessed using an iterator in a Punctuator.