[
https://issues.jboss.org/browse/TEIID-2338?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2338.
-----------------------------------
Fix Version/s: 8.3
Resolution: Done
Addressed by detecting the need for indexes against explicit staging tables. This works
when there are parametrized filters against the staging table with the general assumption
that the parameters are coming from input sets.
There is still some need for the Designer issue to cover more complicated scenarios -
usage of staging tables in subqueries or in joins without input set criteria (although the
latter case could be detected - but was left as a TODO with this issue).
staging table performance
-------------------------
Key: TEIID-2338
URL:
https://issues.jboss.org/browse/TEIID-2338
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.3
Large staging tables should be indexed based upon their usage to improve performance.
Further usage analysis could limit the size of the initial staging table, but is somewhat
complicated - and references can be used in dynamic sql.
--
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