[
https://issues.apache.org/jira/browse/KAFKA-14748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747670#comment-17747670
]
Florin Akermann commented on KAFKA-14748:
-----------------------------------------
I have created a PR for this particular issue.
[https://github.com/apache/kafka/pull/14107]
I am ok with first considering merging when I have addressed the 4 related
issues as well.
Nonetheless it would be great to have some feedback. Just so I know whether I
have understood the scope of this particular item (KAFKA-14748) and what I
should keep in mind for the other incoming merge requests.
> Relax non-null FK left-join requirement
> ---------------------------------------
>
> Key: KAFKA-14748
> URL: https://issues.apache.org/jira/browse/KAFKA-14748
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Florin Akermann
> Priority: Major
>
> Kafka Streams enforces a strict non-null-key policy in the DSL across all
> key-dependent operations (like aggregations and joins).
> This also applies to FK-joins, in particular to the ForeignKeyExtractor. If
> it returns `null`, it's treated as invalid. For left-joins, it might make
> sense to still accept a `null`, and add the left-hand record with an empty
> right-hand-side to the result.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
