[ 
https://issues.apache.org/jira/browse/ASTERIXDB-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871687#comment-17871687
 ] 

ASF subversion and git services commented on ASTERIXDB-3472:
------------------------------------------------------------

Commit 225f47c44434ff7a178caf6c95131482e39cac26 in asterixdb's branch 
refs/heads/master from Ali Alsuliman
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=225f47c444 ]

[ASTERIXDB-3472][HYR] Catch Task exceptions

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
When executing a Task, catch any exception from the different try blocks
to prevent the loss of the original exception.

This patch includes cherry-picks from:
https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/18317

Ext-ref: MB-62949
Change-Id: I5e0f1e6b906c15932a3bb7ae740b5a7c89198cae
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/18565
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Ali Alsuliman <[email protected]>
Reviewed-by: Michael Blow <[email protected]>


> Original exception gets masked by later exception
> -------------------------------------------------
>
>                 Key: ASTERIXDB-3472
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3472
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: HYR - Hyracks
>            Reporter: Ali Alsuliman
>            Assignee: Ali Alsuliman
>            Priority: Major
>              Labels: triaged
>
> When executing the tasks of a query and a failure happens in a task, the 
> original exception can get masked by a later exception leading to the loss of 
> the root cause of the query failure. As an example, when a task encounters a 
> failure during opening its pipeline, the pipeline will be closed as usual 
> (and the failure should be reported). However, if another failure happens 
> during closing the pipeline, this later exception masks the original 
> exception. There is no way to debug such cases any further since the root 
> cause is gone.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to