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.
Attachments
Issue Links
- causes
-
KAFKA-12845 Rollback change which requires join key to be non null on KStream->GlobalKTable
-
- Resolved
-
- links to