Hyunsik Choi created TAJO-165:
---------------------------------
Summary: TajoCli prints wrong execution time.
Key: TAJO-165
URL: https://issues.apache.org/jira/browse/TAJO-165
Project: Tajo
Issue Type: Bug
Components: client
Reporter: Hyunsik Choi
Fix For: 0.2-incubating
See the below tsql (command line interface). Actual response time 91.162 sec,
but the execution time shows wrong time. We should fix it.
{noformat}
Progress: 99%, response time: 87.368 sec
Progress: 99%, response time: 88.369 sec
Progress: 50%, response time: 89.37 sec
Progress: 50%, response time: 90.371 sec
Progress: 100%, response time: 91.162 sec
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/home/hadoop/tajo-0.2.0/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/home/hadoop/hadoop-2.0.3-alpha/share/hadoop/common/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
final state: QUERY_SUCCEEDED, init time: 1.164 sec, execution time: 131.072
sec, total response time: 91.162 sec
result: /tmp/tajo/staging/q_1378472257871_0001/RESULT
l_returnflag, l_linestatus, sum_qty, sum_base_price, sum_disc_price,
sum_charge, avg_qty, avg_price, avg_disc, count_order
-------------------------------
A, F, 3.775127746E9, 5.660776080171001E12, 5.377736381500957E12,
5.592847412832963E12, 25.49937051445789, 38236.11712758738,
0.05000224373362637, 148047880
N, F, 9.8553062E7, 1.4777109838598013E11, 1.403849659650347E11,
1.4599979303277594E11, 25.501556956882876, 38237.19938880454,
0.049985284338054166, 3864590
N, O, 7.431523524E9, 1.1143560368158234E13, 1.058638791018403E13,
1.1009852425613205E13, 25.500039379704713, 38237.27763229936,
0.049997930905666496, 291431845
R, F, 3.775724894E9, 5.661602909220418E12, 5.378513448539941E12,
5.593662133596932E12, 25.50006611522403, 38236.69694068165,
0.05000130427217999, 148067259
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
