Menu
I'm using materialized KTable to use for left join with my KStream(while the stream is the left side).
However, it seem to process immediately, without waiting for the current version of the KTable to load..
I have a lot of values in my source topic for the KTable and when I start the application, a lot of joins fail(well, not really since it is a left join).
Can I make it start in delay so it would wait for the initial topic load?
365
KTable. Only the Kafka Streams DSL has the notion of a KTable . A KTable is an abstraction of a changelog stream, where each data record represents an update.
By default grace period is 24 hours for all windows in other words we allow out-of-order data for up to a day This behavior is now deprecated and additional details are available in the motivation for the KIP Check out KIP-633 for more details. protected static final long.
Kafka Streams is an API for writing client applications that transform data in Apache Kafka. You usually do this by publishing the transformed data onto a new topic. The data processing itself happens within your client application, not on a Kafka broker. Kafka Connect is an API for moving data into and out of Kafka.
KTable is an abstraction of a changelog stream from a primary-keyed table. Each record in this changelog stream is an update on the primary-keyed table with the record key as the primary key.
You could use the GlobalKTable. It waits until all values synchronized.
121
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
