You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Damian Guy (JIRA)" <ji...@apache.org> on 2016/12/13 16:48:59 UTC
[jira] [Updated] (KAFKA-4532) StateStores can be connected to the
wrong source topic resulting in incorrect metadata returned from IQ
[ https://issues.apache.org/jira/browse/KAFKA-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damian Guy updated KAFKA-4532:
------------------------------
Summary: StateStores can be connected to the wrong source topic resulting in incorrect metadata returned from IQ (was: StateStores can be connected to the wrong source topic)
> StateStores can be connected to the wrong source topic resulting in incorrect metadata returned from IQ
> -------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-4532
> URL: https://issues.apache.org/jira/browse/KAFKA-4532
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.10.1.0, 0.10.1.1, 0.10.2.0
> Reporter: Damian Guy
> Assignee: Damian Guy
> Fix For: 0.10.2.0
>
>
> When building a topology with tables and StateStores, the StateStores are mapped to the source topic names. This map is retrieved via {{TopologyBuilder.stateStoreNameToSourceTopics()}} and is used in Interactive Queries to find the source topics and partitions when resolving the partitions that particular keys will be in.
> There is an issue where by this mapping for a table that is originally created with {{builder.table("topic", "table");}}, and then is subsequently used in a join, is changed to the join topic. This is because the mapping is updated during the call to {{topology.connectProcessorAndStateStores(..)}}.
> In the case that the {{stateStoreNameToSourceTopics}} Map already has a value for the state store name it should not update the Map.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)