Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-7577

Semantics of Table-Table Join with Null Message Are Incorrect

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 1.1.0
    • Fix Version/s: None
    • Component/s: streams
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dthomas-trimble Daren Thomas
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: