[teiid-designer-issues] [JBoss JIRA] Updated: (TEIIDDES-767) Staging tables performance appears to be sub-par - should allow for key/index information
[
https://issues.jboss.org/browse/TEIIDDES-767?page=com.atlassian.jira.plug...
]
Steven Hawkins updated TEIIDDES-767:
------------------------------------
Summary: Staging tables performance appears to be sub-par - should allow for key/index
information (was: Staging tables performance appears to be sub-par)
Designer should allow for pk/index metadata on staging tables. The engine will use this
to enhance performance.
Staging tables performance appears to be sub-par - should allow for
key/index information
-----------------------------------------------------------------------------------------
Key: TEIIDDES-767
URL: https://issues.jboss.org/browse/TEIIDDES-767
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 7.0
Reporter: Steven Hawkins
Defect Tracker #20207: While working on the E2E Staging Tables Test Script, Mark Donnelly
noticed the performance was fairly even between docs using staging tables and docs not
using staging tables. I did further research and found the queries ran faster without
staging tables. The email thread is attached (zipped in case the Trakka doesn't like
it).
The Model Project Set is also attached. The VDB's lone binding is defined.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira