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
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
It's fixed in upcoming 3.1 release.
Cf https://issues.apache.org/jira/browse/KAFKA-10847
A stream-(global)table join has different semantics, so I am not sure if
it would help.
One workaround would be to apply a stateful` faltTransformValues()`
after the join to "buffer" all NULL-results an
Hi Miguel,
> Is there a way to force the behavior I need, meaning... using left join
and
a JoinWindows output only one message (A,B) or (A, null)
I think you can try to achieve it by using *KStream-GlobalKTable left join*,
where the GlobalKTable should read all records at the right topic, and then
Hello
I have been developing a Kafka Streams app that takes as input two topics
as KStreams, processes them in some way and joins them and sends the
combined message to an output topic.
Here's some code,
final StreamJoined joinParams =
StreamJoined.with(
STRING_SERDE,
StreamS