[
https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489493#comment-16489493
]
Guozhang Wang commented on KAFKA-4628:
--------------------------------------
Hello Adam,
Here is my estimate on the complexity: implementation wise it would be quite
similar to {{KStreamImpl#globalTableJoin()}}, but the difference is that the
result should be a KTable, not a KStream, and also if the resulted KTable is
materialized, we should update the materialized state store as well (a
reference of this implementation detail would be in
`KTableKTableAbstractJoin`'s extended classes for inner, outer, left joins). I
think depending on your familiarity with the existing Kafka Streams code base
it would be 5 - 8 days.
Since this is a new API you'd also need to file a KIP
(https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals)
for it, and lead the discussion / drive the voting process. It may take you
another day or two since it should be a pretty straight-forward one.
> Support KTable/GlobalKTable Joins
> ---------------------------------
>
> Key: KAFKA-4628
> URL: https://issues.apache.org/jira/browse/KAFKA-4628
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 0.10.2.0
> Reporter: Damian Guy
> Priority: Major
> Labels: needs-kip
>
> 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
(v7.6.3#76005)
