[
https://issues.apache.org/jira/browse/TAJO-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300101#comment-14300101
]
ASF GitHub Bot commented on TAJO-1321:
--------------------------------------
GitHub user jihoonson opened a pull request:
https://github.com/apache/tajo/pull/369
TAJO-1321: Cli prints wrong response time.
As I commented on https://issues.apache.org/jira/browse/TAJO-1321, I made
the Tajo master to set the start time and the finish time.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jihoonson/tajo-2 TAJO-1321
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/369.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #369
----
commit 109cd30f07d21fe11d6fe96c8ca4ff411706ad27
Author: Jihoon Son <[email protected]>
Date: 2015-02-01T07:30:57Z
TAJO-1321
----
> Cli prints wrong response time
> ------------------------------
>
> Key: TAJO-1321
> URL: https://issues.apache.org/jira/browse/TAJO-1321
> Project: Tajo
> Issue Type: Bug
> Components: cli
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Priority: Critical
> Fix For: 0.10
>
>
> When I run Tajo on two different clusters, the cli prints wrong response time.
> Here is examples.
> - Cluster1: the response time decreases when the query is finished.
> {noformat}
> tpch100> select count(*) from customer;
> Progress: 30%, response time: 1.834 sec
> Progress: 30%, response time: 1.834 sec
> Progress: 30%, response time: 2.235 sec
> Progress: 30%, response time: 3.036 sec
> Progress: 43%, response time: 4.037 sec
> Progress: 43%, response time: 5.038 sec
> Progress: 100%, response time: 4.878 sec
> ?count
> -------------------------------
> 15000000
> (1 rows, 4.878 sec, 9 B selected)
> {noformat}
> - Cluster2: the response time jumps when the query is finished.
> {noformat}
> tpch_hdfs> select count(*) from customer;
> Progress: 0%, response time: 0.908 sec
> Progress: 0%, response time: 0.909 sec
> Progress: 0%, response time: 1.31 sec
> Progress: 0%, response time: 2.111 sec
> Progress: 48%, response time: 3.111 sec
> Progress: 100%, response time: 24.104 sec
> ?count
> -------------------------------
> 15000000
> (1 rows, 24.104 sec, 9 B selected)
> {noformat}
> I suspect that the wrong information is stored when the query history is
> written.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
