[
https://issues.jboss.org/browse/TEIIDDES-1255?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-1255:
------------------------------------------
There are some behavioral differences with later versions. All of what Ramesh describes
was on 7.4.
It could be that past 7.4 the query plan logic was cleaned up. Mark can you confirm that
Designer is ensuring that the query is not executed to produce the plan? If so the
relevant changes should be prioritized for a CP.
Execute all did not work until
https://issues.jboss.org/browse/TEIIDDES-1202 in 7.7
Beyond just the simple expectation that the interaction with the scrapbook represents a
single connection/session, it is inefficient to obtain a new connection each time. Unless
there is some DTP is requirement to obtain a new connection each time it would make more
sense to work off of a single one (then transactional statements, temp tables, set
statements, etc. become meaningful when executed singularly).
Execution plan without executing the query
------------------------------------------
Key: TEIIDDES-1255
URL:
https://issues.jboss.org/browse/TEIIDDES-1255
Project: Teiid Designer
Issue Type: Bug
Components: Data Preview, Transformations
Affects Versions: 7.6
Reporter: Ramesh Reddy
Assignee: Mark Drilling
Fix For: 7.7
DTP execution panel, when user right clicks on the query and ask for execution plan then
no execution plan is returned. Only if the user executes the query then the execution
plan, then user requests for plan it is returned. A query plan can be retrived by
excuting
SET NOEXEC ON
<query>
SET NOEXEC OFF
Also, when I tried to manually do the above steps in the DTP SQL Scrap Book, then it
seemed like it is using a separate connection for each of the abouve commands. so to check
that we did
SET NOEXEC OFF
SHOW NOEXEC -> result was -> NULL (should have been ON)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira