tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jihoon Son (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-387) Query is hanging when errors occurs in Query or SubQuery class
Date Fri, 06 Dec 2013 06:55:35 GMT

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

Jihoon Son commented on TAJO-387:

This patch looks good to me.
As Jinho said, however, the patch is successfully applied, but it seems to require to be rebased.
Also, please remove an unused variable, initTime, in QueryStatus.

> Query is hanging when errors occurs in Query or SubQuery class
> --------------------------------------------------------------
>                 Key: TAJO-387
>                 URL: https://issues.apache.org/jira/browse/TAJO-387
>             Project: Tajo
>          Issue Type: Bug
>          Components: master
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>            Priority: Critical
>             Fix For: 0.8-incubating
>         Attachments: TAJO-387.patch
> Currently, Query is hanging when errors occur in Query or SubQuery. This is a critical
> Primarily, this patch fixes many bugs that cause infinite query hanging. In detail, this
patch does as follows:
>  * When there is no result file, Query::buildOrUpdateResultTableDesc causes NPE. This
patch fixes this bug.
>  * A table can be either a file or directory. 
>   ** Before this patch, a table must be a directory.
>  * Add ERROR state to Query
>  * Allow Query to avoid hanging when errors occur
>  * Enable Query to accumulate diagnostic messages.
>  * Add ERROR state to SubQuery
>  * Allow SubQuery to avoid hanging and retrieve resources when errors occur
>  * Enable SubQuery to accumulate diagnostic messages.
>  * Enable TajoCli to get proper error messages (e.g., Query Failed! or Internal Error!)
when a query is failed or faces internal errors.

This message was sent by Atlassian JIRA

View raw message