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

Posted to jira@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2019/11/01 06:43:00 UTC

[jira] [Commented] (KAFKA-6542) Tables should trigger joins too, not just streams

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

Matthias J. Sax commented on KAFKA-6542:
----------------------------------------

KTables are not really bootstrapped -- compare KAFKA-4113 for a detailed discussion.

>  The code appears to only get to a State.Running when all kTable partitions have been restored.

Correct, but this describes only the failure case scenario. If recovery if required, the "current" KTable state would be fully loaded by re-reading the changelog topic before processing continues.

But this does not happen is you start a new application; a new application will have an empty KTable state when it's started.

> Tables should trigger joins too, not just streams
> -------------------------------------------------
>
>                 Key: KAFKA-6542
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6542
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 1.1.0
>            Reporter: Antony Stubbs
>            Priority: Major
>
> At the moment it's quite possible to have a race condition when joining a stream with a table, if the stream event arrives first, before the table event, in which case the join will fail.
> This is also related to bootstrapping KTables (which is what a GKTable does).
> Related to: KAFKA-4113 Allow KTable bootstrap



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