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:58:00 UTC
[jira] [Commented] (KAFKA-5876) IQ should throw different
exceptions for different errors
[ https://issues.apache.org/jira/browse/KAFKA-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16344789#comment-16344789 ]
Pegerto Fernandez commented on KAFKA-5876:
------------------------------------------
Hi,
In addition to the original comment.
When the local store is not created, or isĀ not yet assign to a task. InvalidStateStoreException its ambiguous and do not provide information about a not existing vs not available datastore.
Regards
> IQ should throw different exceptions for different errors
> ---------------------------------------------------------
>
> Key: KAFKA-5876
> URL: https://issues.apache.org/jira/browse/KAFKA-5876
> Project: Kafka
> Issue Type: Task
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Vito Jeng
> Priority: Major
> Labels: needs-kip, newbie++
> Fix For: 1.2.0
>
>
> Currently, IQ does only throws {{InvalidStateStoreException}} for all errors that occur. However, we have different types of errors and should throw different exceptions for those types.
> For example, if a store was migrated it must be rediscovered while if a store cannot be queried yet, because it is still re-created after a rebalance, the user just needs to wait until store recreation is finished.
> There might be other examples, too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)