[
https://issues.apache.org/jira/browse/HBASE-23910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack updated HBASE-23910:
----------------------------------
Description: This came up in the review of HBASE-23904 where in one
location, we swapped out the old Callable for a different idiom. The refactor
happened to let out RuntimeExceptions rather than wrap them as we've done up to
this. Discussion in the issue wondered if this not the proper behavior. This
issue is about deciding if it is the case and if so, then the retrofit of the
code base to not wrap REs in IOEs.
Environment: (was: This came up in the review of HBASE-23904 where in
one location, we swapped out the old Callable for a different idiom. The
refactor happened to let out RuntimeExceptions rather than wrap them as we've
done up to this. Discussion in the issue wondered if this not the proper
behavior. This issue is about deciding if it is the case and if so, then the
retrofit of the code base to not wrap REs in IOEs.)
> Revisit Callable converting all exceptions (including Runtimes) to IOE
> ----------------------------------------------------------------------
>
> Key: HBASE-23910
> URL: https://issues.apache.org/jira/browse/HBASE-23910
> Project: HBase
> Issue Type: Improvement
> Reporter: Michael Stack
> Priority: Major
>
> This came up in the review of HBASE-23904 where in one location, we swapped
> out the old Callable for a different idiom. The refactor happened to let out
> RuntimeExceptions rather than wrap them as we've done up to this. Discussion
> in the issue wondered if this not the proper behavior. This issue is about
> deciding if it is the case and if so, then the retrofit of the code base to
> not wrap REs in IOEs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
