[
https://issues.apache.org/jira/browse/TAJO-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyunsik Choi resolved TAJO-524.
-------------------------------
Resolution: Fixed
If so, I close this issue.
This may be indirectly caused by other problem like OOM that we dealt with
TAJO-522 and TAJO-537.
However, we can know that Query and Subquery does not handle these situations
and does not show exact cause in the case where OOM is caused. According to the
command line, it just printed QUERY_SUCCEEDED.
So, I'll create another jira issue for handling exceptions those cases.
> zero result
> ------------
>
> Key: TAJO-524
> URL: https://issues.apache.org/jira/browse/TAJO-524
> Project: Tajo
> Issue Type: Bug
> Components: distributed query plan
> Affects Versions: 0.8-incubating
> Reporter: Min Zhou
>
> I ran a simple count query, but get zero result.
> {noformat}
> tajo> select count(1) from supplier ;
> Progress: 0%, response time: 0.998 sec
> 25.107: [GC 25.107: [ParNew: 17961K->960K(19136K), 0.0033390 secs]
> 19419K->2430K(128960K), 0.0034390 secs] [Times: user=0.03 sys=0.01, real=0.00
> secs]
> Progress: 7%, response time: 2.034 sec
> Progress: 14%, response time: 3.059 sec
> Progress: 14%, response time: 4.084 sec
> Progress: 14%, response time: 5.109 sec
> Progress: 14%, response time: 6.135 sec
> Progress: 100%, response time: 6.582 sec
> final state: QUERY_SUCCEEDED, response time: 6.582 sec
> result:
> hdfs://esv4-hcl280.grid.linkedin.com:8020/user/mzhou/tajo/staging/q_1390180401396_0002/RESULT,
> 0 rows (0 B)
> ?count
> -------------------------------
> {noformat}
> Look into hdfs , this file is zero bytes.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
