[
https://issues.jboss.org/browse/TEIID-2790?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2790:
---------------------------------------
We could add logic to delay/asynchly load stats on import and an option to load stats on
startup. The issue with the latter is that in general our metadata is not in a format
conducive toward using database specific logic - the name in source is not generally
guaranteed to be in a specific format (and we really want it in terms of its name
components). If it's not in a format such that the schema name is readily separable,
then the best we can do is issue an aggregate query which can be quite expensive. An in
between approach would be to add catalog/schema/table name as extension properties on the
table at import time to make subsequent logic easier.
I also need to look at expanding the applicable sources for stats gathering and adding the
column stats logic for oracle.
Add more options for costing during import
------------------------------------------
Key: TEIID-2790
URL:
https://issues.jboss.org/browse/TEIID-2790
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector, Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7
With many jdbc sources full cardinality is reported from the index info for non
statistical indexes (such as mysql). This should be used to set the cardinality of the
table. Failing that there should be an option to use an aggregate call or other source
stats.
This is not quite the same as TEIID-245 as it's happening at import time, but the two
do overlap.
--
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