[
https://issues.apache.org/jira/browse/KAFKA-10277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-10277:
------------------------------------
Description:
In general, Kafka Streams requires that key and value are non-null for
aggregations and join input records. While this requirement is reasonable in
general, for KStream-GlobalKTable joins it's questionable for the stream input
record key. The join is based on a `keySelector` and it seems to be sufficient
to require that the `keySelector` returns a not-null join-key for the stream
record.
We should consider to relax the non-null key requirement for stream-side input
records.
was:
In general, Kafka Streams requires that key and value are non-null for
aggregations and join input records. While this requirement is reasonable in
general, for stream-globalKTable joins it's questionable for the stream input
record key. The join is based on a `keySelector` and it seems to be sufficient
to require that the `keySelector` returns a not-null join-key for the stream
record.
We should consider to relax the non-null key requirement for stream-side input
records.
> Relax non-null key requirement for KStream-GlobalKTable joins
> -------------------------------------------------------------
>
> Key: KAFKA-10277
> URL: https://issues.apache.org/jira/browse/KAFKA-10277
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Priority: Major
>
> In general, Kafka Streams requires that key and value are non-null for
> aggregations and join input records. While this requirement is reasonable in
> general, for KStream-GlobalKTable joins it's questionable for the stream
> input record key. The join is based on a `keySelector` and it seems to be
> sufficient to require that the `keySelector` returns a not-null join-key for
> the stream record.
> We should consider to relax the non-null key requirement for stream-side
> input records.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
