[teiid-issues] [JBoss JIRA] (TEIID-5174) Filter internal constructs from oracle metadata

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-5174.
-----------------------------------
    Fix Version/s: 10.0.3
       Resolution: Done


Changed the oracle import to always filter the SYS schema.  Also changed the import logic to not use the one shot import of columns, and instead always fetch per table as that was a significant performance issue for oracle and is generally not enough of a performance benefit to use for other databases as column information will be indexed by schema/table names.

> Filter internal constructs from oracle metadata
> -----------------------------------------------
>
>                 Key: TEIID-5174
>                 URL: https://issues.jboss.org/browse/TEIID-5174
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: JDBC Connector
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 10.1, 10.0.3
>
>
> Even with the import table types set to TABLE, an Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 accessed with the 12.1.0.1.0 driver will contain internal tables which will cause the deployment to error:
> TEIID31071 Invalid table; Table oracleModel.HS_PARTITION_COL_NAME has no columns defined
> It would be good if these were filtered by default.  The workaround is to specify a schema or regex to prevent such tables from being imported.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)