Yeah the semantics are slightly different. For a KTable, a null value just
means that the record is a tombstone, and will be anyways ignored by subsequent
processing:
http://docs.confluent.io/current/streams/javadocs/org/apache/kafka/streams/kstream/KTable.html#filter-org.apache.kafka.streams.kst
Hi all,
I was asking why the different behaviour of filter() operation on a KStream and
KTable.
On KStream, if the predicate is false, the message isn't passed to the next
node (so for example if a sinknode, it doesn't arrive to the destination topic).
On KTable, if the predicate is true, a m
