[
https://issues.apache.org/jira/browse/FLINK-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878022#comment-15878022
]
ASF GitHub Bot commented on FLINK-5865:
---------------------------------------
Github user shixiaogang commented on the issue:
https://github.com/apache/flink/pull/3380
I like the idea of find some more "specific" exceptions. Flink can define
some specific Exceptions like `StateAccessException`. That may help better
understand the code.
I am also thinking that it's better not to put any exception in the
signature of user-facing interfaces like `State`. All exceptions thrown by
these methods are `RuntimeException` which are caught and handled by Flink.
It's because these methods provided by Flink are supposed to work properly and
do not throw any exception. Actually, users can do few things even if they can
catch the exceptions.
> Throw original exception in states
> ----------------------------------
>
> Key: FLINK-5865
> URL: https://issues.apache.org/jira/browse/FLINK-5865
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing
> Affects Versions: 1.3.0
> Reporter: Xiaogang Shi
> Assignee: Xiaogang Shi
>
> Now all exception thrown in RocksDB states are converted to
> {{RuntimeException}}. It's unnecessary and will print useless stacks in the
> log.
> I think it's better to throw the original exception, without any wrapping.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
