query stats are not published to METRIC_QUERY_TABLE if the query time is greater than STATISTICSLIMIT and smaller than STATISTICSINTERVAL
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Trafodion |
Fix Committed
|
High
|
Judy Zhao |
Bug Description
Here are the parameters.
mxosrvr -ZKHOST n007.cm.
This one was published
SQL>insert into VITO_TEST.tab1 select colint, 'a' from VITO_TEST.fun f where f.colint < 100000000;
--- 15625 row(s) inserted.
Start Time 2015/03/19 05:51:08.266558
End Time 2015/03/19 05:52:38.551538
Elapsed Time 00:01:30.284980
Compile Time 00:00:00.047735
Execution Time 00:01:30.236976
But this one was not in the table
SQL>insert into VITO_TEST.tab1 select colint, 'a' from VITO_TEST.fun f where f.colint < 100000;
--- 3125 row(s) inserted.
Start Time 2015/03/19 05:46:21.893948
End Time 2015/03/19 05:46:27.043882
Elapsed Time 00:00:05.149934
Compile Time 00:00:00.011382
Execution Time 00:00:05.138318
tags: | added: connectivity-mxosrvr |
Changed in trafodion: | |
importance: | Undecided → High |
assignee: | nobody → Judy Zhao (hongxia-zhao) |
status: | New → In Progress |
milestone: | none → r1.1 |
Changed in trafodion: | |
milestone: | r1.1 → r2.0 |
Changed in trafodion: | |
status: | In Progress → Fix Committed |
After discussions with dev, this is the understanding: The STATISTICSINTERVAL time does not apply to query statistics, it is the interval used for query aggregation to be published in METRIC_ QUERY_AGGR_ TABLE. For query stats, only STATISTICSLIMIT time should be used, if the query runs longer than the limit time, stats should get published in metric_query_table.
So, from the bug it looks like STATISTICSINTERVAL time is being used for query stats instead of STATISTICSLIMIT time.