Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Fri, 2 Sep 2016 10:21:21 +0000 (UTC)
From: "Matthias J. Sax (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.13002150.1472755279000.477831.1472811681286@Atlassian.JIRA>
In-Reply-To: <JIRA.13002150.1472755279000@Atlassian.JIRA>
References: <JIRA.13002150.1472755279000@Atlassian.JIRA> <JIRA.13002150.1472755279827@arcas>
Subject: [jira] [Commented] (KAFKA-4113) Allow KTable bootstrap
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 02 Sep 2016 10:21:23 -0000


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

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

Thanks for pointing out! I read it once. Good post! :)

> Allow KTable bootstrap
> ----------------------
>
>                 Key: KAFKA-4113
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4113
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>            Reporter: Matthias J. Sax
>            Assignee: Guozhang Wang
>
> On the mailing list, there are multiple request about the possibility to "fully populate" a KTable before actual stream processing start.
> Even if it is somewhat difficult to define, when the initial populating phase should end, there are multiple possibilities:
> The main idea is, that there is a rarely updated topic that contains the data. Only after this topic got read completely and the KTable is ready, the application should start processing. This would indicate, that on startup, the current partition sizes must be fetched and stored, and after KTable got populated up to those offsets, stream processing can start.
> Other discussed ideas are:
> 1) an initial fixed time period for populating
> (it might be hard for a user to estimate the correct value)
> 2) an "idle" period, ie, if no update to a KTable for a certain time is
> done, we consider it as populated
> 3) a timestamp cut off point, ie, all records with an older timestamp
> belong to the initial populating phase
> The API change is not decided yet, and the API desing is part of this JIRA.
> One suggestion (for option (4)) was:
> {noformat}
> KTable table = builder.table("topic", 1000); // populate the table without reading any other topics until see one record with timestamp 1000.
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)