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

Posted to jira@kafka.apache.org by "Pegerto Fernandez (JIRA)" <ji...@apache.org> on 2018/01/30 09:47:00 UTC

[jira] [Resolved] (KAFKA-6497) streams#store ambiguous InvalidStateStoreException

     [ https://issues.apache.org/jira/browse/KAFKA-6497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pegerto Fernandez resolved KAFKA-6497.
--------------------------------------
    Resolution: Duplicate

> streams#store ambiguous InvalidStateStoreException
> --------------------------------------------------
>
>                 Key: KAFKA-6497
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6497
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 1.0.0
>            Reporter: Pegerto Fernandez
>            Priority: Major
>
> When using the streams API.
> When deploy new materialised views, the access to the store provide always InvalidStateStoreExeception, that can be cause by a rebalance, but it is also caused by not execute the topology that create the view. For example and empty topic.
>  
> In this case, when there topology is running, but the local store do not contain any data, the behaviour should be different, for example wait versus assume the expected key to be not found. 
>  
> I am relative new to streams so please correct me if I miss something.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)