You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2019/02/02 06:37:00 UTC
[jira] [Updated] (HBASE-21827) CompletableFuture may wrap the
original Throwable with CompletionException while propagating it
[ https://issues.apache.org/jira/browse/HBASE-21827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-21827:
------------------------------
Fix Version/s: (was: 2.3.0)
(was: 2.2.0)
(was: 3.0.0)
> CompletableFuture may wrap the original Throwable with CompletionException while propagating it
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-21827
> URL: https://issues.apache.org/jira/browse/HBASE-21827
> Project: HBase
> Issue Type: Bug
> Components: asyncclient, Client
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Critical
>
> See the stack overflow post
> https://stackoverflow.com/questions/49230980/does-completionstage-always-wrap-exceptions-in-completionexception
> It seems that, for a chain of CompletableFutures, the first child will receive the original exception, and the latter ones will receive a CompletionException, which is the wrapper of the original exception.
> This is also what I observed when debugging HBASE-21779. We need to fix this, at least, we should unwrap it when we want to return exceptions to users.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)