[
https://issues.apache.org/jira/browse/KAFKA-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384726#comment-15384726
]
ASF GitHub Bot commented on KAFKA-3911:
---------------------------------------
GitHub user enothereska opened a pull request:
https://github.com/apache/kafka/pull/1638
KAFKA-3911: Initial source materialization (WiP)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/enothereska/kafka
KAFKA-3911-ktable-materialization
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1638.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1638
----
commit 01d7ef659acd790096f030a54d2bf2e121252996
Author: Eno Thereska <eno.there...@gmail.com>
Date: 2016-07-18T20:13:25Z
Initial source materialization
----
> Enforce KTable materialization
> ------------------------------
>
> Key: KAFKA-3911
> URL: https://issues.apache.org/jira/browse/KAFKA-3911
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Affects Versions: 0.10.1.0
> Reporter: Eno Thereska
> Assignee: Eno Thereska
> Fix For: 0.10.1.0
>
>
> Always enforce KTable materialization upon creation (i.e. even for
> "builder.table(..).to()" we also materialize it into a state store; this will
> indeed incur unnecessary overhead but should be very rare, and it helps for
> consistency of materialization).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
