Xiangdong Huang created IOTDB-378:
-------------------------------------
Summary: Query duration is incorrect in Metric module and the WebUI
Key: IOTDB-378
URL: https://issues.apache.org/jira/browse/IOTDB-378
Project: Apache IoTDB
Issue Type: Bug
Affects Versions: 0.8.2, 0.8.1, 0.9.0, 0.8.0
Reporter: Xiangdong Huang
see the code:
{code:java}
// code placeholder
PhysicalPlan physicalPlan;
physicalPlan = processor.parseSQLToPhysicalPlan(statement,
sessionIdZoneIdMap.get(req.getSessionId()));
if (physicalPlan.isQuery()) {
resp = executeQueryStatement(req.statementId, physicalPlan,
sessionIdUsernameMap.get(req.getSessionId()));
long endTime = System.currentTimeMillis();
sqlArgument = new SqlArgument(resp, physicalPlan, statement, startTime,
endTime);
sqlArgumentsList.add(sqlArgument);
if (sqlArgumentsList.size() > MAX_SIZE) {
sqlArgumentsList.subList(0, DELETE_SIZE).clear();
}
return resp;
} else {
return executeUpdateStatement(physicalPlan, req.getSessionId());
}
{code}
The time cost just contains generating a physical plan...
Should we modify it to the real execution time of a query?
Or, show 3 parts: "generate the physical plan", "find the first data records",
"finished"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
