[
https://issues.jboss.org/browse/TEIID-3637?page=com.atlassian.jira.plugin...
]
Jorge Herrera commented on TEIID-3637:
--------------------------------------
Van is correct, it still does not show the info we are after.
But one thing with that approach of using the NOEXEC ON, is that you have to turn it on
and then off when you want to actually execute the query, I know its easy enough, its just
that in other DBs you only have to add the word 'explain' before the query, and it
will give you the plan.
Query Plan/Execution Plan Enhancements
--------------------------------------
Key: TEIID-3637
URL:
https://issues.jboss.org/browse/TEIID-3637
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 8.7.1
Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
JBoss Data Virtualization 6.1.0.ER4
Reporter: Jorge Herrera
Assignee: Steven Hawkins
Priority: Critical
Query Plan / Execution plan, for any particular query is lacking more explicit
information about what the query engine is doing for each query. Would like to know if its
JDV doing the processing vs doing push down optimization, and what is the path it takes if
its internal to JDV, and also the costs associated with every step.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)