You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Daren Thomas (JIRA)" <ji...@apache.org> on 2018/11/01 16:41:00 UTC

[jira] [Commented] (KAFKA-7577) Semantics of Table-Table Join with Null Message Are Incorrect

    [ https://issues.apache.org/jira/browse/KAFKA-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671844#comment-16671844 ] 

Daren Thomas commented on KAFKA-7577:
-------------------------------------

I see similar behavior with the right side of the Left Join.  If the message value is null, the Left Join is not processed.

> Semantics of Table-Table Join with Null Message Are Incorrect
> -------------------------------------------------------------
>
>                 Key: KAFKA-7577
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7577
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Daren Thomas
>            Priority: Major
>
> Observed behavior of Table-Table join with a Null Message does not match the semantics described in the documentation ([https://docs.confluent.io/current/streams/developer-guide/dsl-api.html#ktable-ktable-join).]  The expectation is:
>  * Message A results in [A, null] from the Left Join
>  * Message null (tombstone) results in null (tombstone) from the Left Join
>  The observed behavior was that the null (tombstone) message did not pass through the Left Join to the output topic like expected.  This behavior was observed with and without caching enabled, against a test harness, and against a local Confluent 5.0.0 platform.  It was also observed that the KTableKTableLeftJoinProcessor.process() function was not called for the null (tombstone) message.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)