[
https://issues.jboss.org/browse/TEIID-2409?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2409:
-------------------------------------
IMO, there is not much use in adding multiple of these calls, in TEIID-2408 we are adding
the couple wait queue stats, that should tell you if there is waiting of plans occurring,
and their average times. The general goal is to make wait times less or not existent. So,
you need configure for such scenario.
When PLAN USER COMMAND is printed, the planning is already done. So, from start to plan
print outs is Teiid overhead. Also, did you look at getPlanDescription() on your statement
object, it has some statistics on them, may be we could any fine grained stats there
instead.
To add execution id into data src command_log
---------------------------------------------
Key: TEIID-2409
URL:
https://issues.jboss.org/browse/TEIID-2409
Project: Teiid
Issue Type: Feature Request
Affects Versions: 8.2
Reporter: Jack Ma
Assignee: Steven Hawkins
When we try to analyze the command_log, for some user query, it push multiple data source
queries to same data source, in this case, both request id and source command id are same,
so it is impossible to pair those data source queries from the command_log (please see
discussion:
https://community.jboss.org/message/799183#799183). Adding the execution id
into the data source command_log should make following combination key unique (request id
+ source command id + execution id)
--
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