[
https://issues.jboss.org/browse/TEIID-2475?page=com.atlassian.jira.plugin...
]
Steven Hawkins reopened TEIID-2475:
-----------------------------------
The stat logic was actually a little more convoluted than first thought, as the process
time includes the total wall clock time and thus may result in negative values for unions
(which is why the workaround was added to begin with). In general the computation of the
current notion of the node's "process time" needs tweaked.
The RelationalNode.collectNodeStats is only subtracting out the last
node
-------------------------------------------------------------------------
Key: TEIID-2475
URL:
https://issues.jboss.org/browse/TEIID-2475
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Fix For: 8.4, 7.7.8
Attachments: Query_Plan.txt
The "Node Cumulative Next Batch Process Time" Statistic
If you have a look at the explain plan (attached). Following the definition,
the JoinNode Node Cumulative Next Batch Process Time: 565471. So, it is the summation of
AccessNode (Node Process Time: 892860) + DependentAccessNode (Node Process Time: 439) +
JoinNode (Node Process Time: 2203120). The summation does not agree.
The RelationalNode.collectNodeStats looks wrong (it's effectively only subtracting
out the last node)
--
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