[
https://issues.apache.org/jira/browse/KAFKA-16644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842417#comment-17842417
]
Matthias J. Sax commented on KAFKA-16644:
-----------------------------------------
Thanks for the pointer. I did not have time yet to dig into the details of
K16394... If that's the case, we can close this as duplicate; will take care of
it after I read up on K16394.
> FK join emits duplicate tombstone on left-side delete
> -----------------------------------------------------
>
> Key: KAFKA-16644
> URL: https://issues.apache.org/jira/browse/KAFKA-16644
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 3.7.0
> Reporter: Matthias J. Sax
> Priority: Major
>
> We introduced a regression bug in 3.7.0 release via KAFKA-14778. When a
> left-hand side record is deleted, the join now emits two tombstone records
> instead of one.
> The problem was not detected via unit test, because the tests use a `Map`
> instead of a `List` when verifying the result topic records
> ([https://github.com/apache/kafka/blob/trunk/streams/src/test/java/org/apache/kafka/streams/integration/KTableKTableForeignKeyJoinIntegrationTest.java#L250-L255).]
> We should update all test cases to use `List` when reading from the output
> topic, and of course fix the introduced bug: The
> `SubscriptionSendProcessorSupplier` is sending two subscription records
> instead of just a single one:
> [https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/kstream/internals/foreignkeyjoin/SubscriptionSendProcessorSupplier.java#L133-L136]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
