From 6f8d61a5f0c86cf2d207c9a138a5fc19022382bc Mon Sep 17 00:00:00 2001
From: Florin Akermann The join will be triggered under the conditions listed below whenever new input is received. When it is triggered, the user-supplied
ValueJoiner
will be called to produce
join output records.
++
+- Input records with a
+null
value are ignored and do not trigger the join.
For each input record on the left side that does not have any match on the right side, the ValueJoiner
will be called with ValueJoiner#apply(leftRecord.value, null)
;
this explains the row with timestamp=60 and timestampe=80 in the table below, which lists [E, null]
and [F, null]
in the LEFT JOIN column.
@@ -1947,6 +1952,11 @@
ValueJoiner
will be called to produce
join output records.
+ ++
+- Input records with a
+null
value are ignored and do not trigger the join.
For each input record on one side that does not have any match on the other side, the ValueJoiner
will be called with ValueJoiner#apply(leftRecord.value, null)
or
ValueJoiner#apply(null, rightRecord.value)
, respectively; this explains the row with timestamp=60, timestamp=80, and timestamp=100 in the table below, which lists [E, null]
,
@@ -2532,6 +2542,10 @@
+
- + Records for which the
foreignKeyExtractor
producesnull
are ignored and do not trigger a join. + If you want to join withnull
foreign keys, use a suitable sentinel value to do so (i.e."NULL"
for a String field, or-1
for an auto-incrementing integer field). +- Input records with a
null
value are interpreted as tombstones @@ -2591,10 +2605,6 @@KTable-KTable Foreign-Key
-
- - Records for which the
foreignKeyExtractor
producesnull
are ignored and do not trigger a join. - If you want to join withnull
foreign keys, use a suitable sentinel value to do so (i.e."NULL"
for a String field, or-1
for an auto-incrementing integer field). -- Input records with a
null
value are interpreted as tombstones