You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/02 14:00: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=17049230#comment-17049230 ]
ASF GitHub Bot commented on KAFKA-5876:
---------------------------------------
vitojeng commented on pull request #8200: KAFKA-5876: IQ should throw different exceptions for different errors
URL: https://github.com/apache/kafka/pull/8200
[KIP-216: IQ should throw different exceptions for different errors](https://cwiki.apache.org/confluence/display/KAFKA/KIP-216%3A+IQ+should+throw+different+exceptions+for+different+errors)
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> 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++
>
> 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
(v8.3.4#803005)