[
https://issues.jboss.org/browse/TEIID-2790?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2790:
-------------------------------------
I thought we have extension properties for the catalog/schema, if not adding them is good
idea on the table. If we go async route, I say we make available for execution through
system procedure execution for ad-hoc. How are you thinking of persistence of stats if it
was done after the import?
Other ways to manually input table stats for runtime would be
* web-console
* vdb.xml
* admin-api
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