[
https://issues.apache.org/jira/browse/KAFKA-6497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343826#comment-16343826
]
Matthias J. Sax commented on KAFKA-6497:
----------------------------------------
[~Pegerto] Thanks for filing this ticket. I am wondering if
https://issues.apache.org/jira/browse/KAFKA-5876 does actually cover what you
describe here? Maybe we should close this as a duplicate and you can comment on
KAFKA-5876 instead so we can include this (seems, the case you describe in not
mentioned there yet).
> 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)
