[teiid-issues] [JBoss JIRA] (TEIID-2790) Add more options for costing during import

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935090#comment-12935090 ] 

Steven Hawkins commented on TEIID-2790:
---------------------------------------

Added an initial checkin with two new jdbc import properties:

useAnyIndexCardinality  (defaults to false) - when importKeys or importIndex is enable and the database does not support statistical indexes (off-hand oracle is the only one that I know of that does) then we'll use the maximum cardinality reported on the other indexes as the table cardinality.  For databases such as mysql this is typically sufficient to determine the cardinality provided an index of any kind exists.

importStatistics (defaults to false) - initially supported by only oracle and mysql.  For tables that do not have a cardinality set (which may be due to not using the useAnyIndexCarinality setting or not importing indexes) we'll use the database statistically information to determine the cardinality.  We'll look at adding the column statistics at a later time.
                
> 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