[
https://issues.apache.org/jira/browse/HBASE-21827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829060#comment-16829060
]
Duo Zhang commented on HBASE-21827:
-----------------------------------
This could be a long term problem if we keep using CompletableFuture. Anyway I
think we can resolve this issue for now, can open new issues if we hit this
problem again in the future.
> 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: Umbrella
> 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)
