[jira] [Commented] (KAFKA-4628) Support KTable/GlobalKTable Joins

["Dmitry Minkovsky (JIRA)" <ji...@apache.org>]

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

Dmitry Minkovsky commented on KAFKA-4628:
-----------------------------------------

on KAFKA-4880 (a dupe of this ticket), Michale Noll writes:

> FWIW, I wonder how much interest there actually is for this functionality. Users have been requesting stream-globalTable joins, but personally I have yet to run into a person that wants table-globalTable joins. Just saying.

I hadn't noticed that GlobalKTables were severely limited and assumed they had all the functionality of regular tables. I had been really excited to use them for "hydration" or denormalization. I have two models which will be present in my application in different quantities. Instances of one model will be very few in quantity compared to instances of the second model. I want to "hydrate" instances of the high-quantity model with instances of the low-quantity model, which can be available in its entirety at all instances. KTable/KTable joins are great for denormalization because you can drive the update from both sides of the relationship. KTable/GlobalKTable joins would facilitates such updates while removing the need to repartition the left table. 

> Support KTable/GlobalKTable Joins
> ---------------------------------
>
>                 Key: KAFKA-4628
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4628
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>    Affects Versions: 0.10.2.0
>            Reporter: Damian Guy
>             Fix For: 0.11.1.0
>
>
> In KIP-99 we have added support for GlobalKTables, however we don't currently support KTable/GlobalKTable joins as they require materializing a state store for the join. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)