You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2013/12/05 16:44:35 UTC
[jira] [Updated] (TAJO-387) Query is hanging when errors occurs in
Query or SubQuery class
[ https://issues.apache.org/jira/browse/TAJO-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyunsik Choi updated TAJO-387:
------------------------------
Summary: Query is hanging when errors occurs in Query or SubQuery class (was: Query is hanging when errors occurs in Query or SubQuery)
> 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 bug.
> 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
(v6.1#6144)