[
https://issues.apache.org/jira/browse/TAJO-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301092#comment-14301092
]
Tajo QA commented on TAJO-1321:
-------------------------------
{color:red}*-1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12695890/TAJO-1321.patch
against master revision release-0.9.0-rc0-161-g1e00759.
{color:green}+1 @author.{color} The patch does not contain any @author
tags.
{color:red}-1 tests included.{color} The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac.{color} The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc.{color} The applied patch does not increase the
total number of javadoc warnings.
{color:green}+1 checkstyle.{color} The patch generated 0 code style errors.
{color:red}-1 findbugs.{color} The patch appears to introduce 159 new
Findbugs (version 2.0.3) warnings.
{color:red}-1 release audit.{color} The applied patch generated 882
release audit warnings.
{color:green}+1 core tests.{color} The patch passed unit tests in
tajo-core.
Test results:
https://builds.apache.org/job/PreCommit-TAJO-Build/581//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-TAJO-Build/581//artifact/incubator-tajo/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TAJO-Build/581//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core.html
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/581//console
This message is automatically generated.
> Cli prints wrong response time
> ------------------------------
>
> Key: TAJO-1321
> URL: https://issues.apache.org/jira/browse/TAJO-1321
> Project: Tajo
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.10
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Priority: Critical
> Fix For: 0.10
>
> Attachments: TAJO-1321.patch
>
>
> 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)
