You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Pedro Gontijo (Jira)" <ji...@apache.org> on 2021/05/25 17:25:00 UTC

[jira] [Commented] (KAFKA-12845) Rollback change which requires join key to be non null on KStream->GlobalKTable

    [ https://issues.apache.org/jira/browse/KAFKA-12845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351227#comment-17351227 ] 

Pedro Gontijo commented on KAFKA-12845:
---------------------------------------

[~mjsax] and [~JoelWee] it would be great o hear your thoughts on this.

> Rollback change which requires join key to be non null on KStream->GlobalKTable
> -------------------------------------------------------------------------------
>
>                 Key: KAFKA-12845
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12845
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 2.7.0
>            Reporter: Pedro Gontijo
>            Priority: Major
>
> As part of [KAFKA-10277|https://issues.apache.org/jira/browse/KAFKA-10277] the behavior for KStream->GlobalKtable joins was changed to require non null join keys.
> But it seems reasonable that not every record will have an existing relationship (and hence a key) with the join globalktable. Think about a User>Car for instance, or PageView>Product. An empty/zero key could be returned by the KeyMapper but that will make a totally unnecessary search into the store.
> I do not think that makes sense for any GlobalKtable join (inner or left) but for left join it sounds even more strange.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)