drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Westin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-2699) Collect all cleanup errors before reporting a failure to the client
Date Wed, 01 Jul 2015 22:59:04 GMT

    [ https://issues.apache.org/jira/browse/DRILL-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611129#comment-14611129

Chris Westin commented on DRILL-2699:

It seems like the DeferredException class should be handling this now, so I would say yes,
this will address the issue.

> Collect all cleanup errors before reporting a failure to the client
> -------------------------------------------------------------------
>                 Key: DRILL-2699
>                 URL: https://issues.apache.org/jira/browse/DRILL-2699
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Execution - Flow
>    Affects Versions: 0.8.0
>            Reporter: Deneche A. Hakim
>            Assignee: Deneche A. Hakim
>             Fix For: 1.2.0
> If a query fails, the fragments and foreman should make sure to collect all failures
and report them back to the client. Some known places where this isn't respected:
> - If a fragment fails, it will report the failure to the foreman before cleaning up.
Any failure that happens in the cleanup process will be dropped by the foreman.
> - If multiple fragments fail, the Foreman will only report to the user the first failure
it received and close immediately. All other failures will be dropped.

This message was sent by Atlassian JIRA

View raw message