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

Jinho Kim commented on TAJO-1308:
---------------------------------

Additionally, I’ve fix the error message issue when query is failed.
{noformat}
ERROR: org.apache.tajo.rpc.TajoServiceException: Message missing required 
fields: resultSet
java.sql.SQLException: org.apache.tajo.rpc.TajoServiceException: Message 
missing required fields: resultSet
        at 
org.apache.tajo.jdbc.TajoResultSetBase.next(TajoResultSetBase.java:786)
        at 
org.apache.tajo.cli.tsql.DefaultTajoCliOutputFormatter.printResult(DefaultTajoCliOutputFormatter.java:104)
        at 
org.apache.tajo.cli.tsql.TajoCli.localQueryCompleted(TajoCli.java:571)
        at org.apache.tajo.cli.tsql.TajoCli.executeQuery(TajoCli.java:545)
        at 
org.apache.tajo.cli.tsql.TajoCli.executeParsedResults(TajoCli.java:447)
        at org.apache.tajo.cli.tsql.TajoCli.runShell(TajoCli.java:419)
        at org.apache.tajo.cli.tsql.TajoCli.main(TajoCli.java:699)
Caused by: java.io.IOException: org.apache.tajo.rpc.TajoServiceException: 
Message missing required fields: resultSet
        at org.apache.tajo.jdbc.FetchResultSet.nextTuple(FetchResultSet.java:81)
        at 
org.apache.tajo.jdbc.TajoResultSetBase.next(TajoResultSetBase.java:780)
        ... 6 more
{noformat}
https://github.com/apache/tajo/pull/329

> QueryInprogress can not release when query is QUERY_ERROR
> ---------------------------------------------------------
>
>                 Key: TAJO-1308
>                 URL: https://issues.apache.org/jira/browse/TAJO-1308
>             Project: Tajo
>          Issue Type: Bug
>          Components: query master, tajo master
>    Affects Versions: 0.10
>            Reporter: Jinho Kim
>            Assignee: Jinho Kim
>            Priority: Critical
>
> See the title.
> The main problem is caused by a missing {{QUERY_ERROR}}, It will be resource 
> leak.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to