[
https://jira.jboss.org/jira/browse/TEIID-687?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-687.
----------------------------------
Resolution: Done
Add metadata import capabilities to the JDBCConnector through the JDBCMetadataProcessor,
which walks the DatabaseMetadata. Possible import settings (specified through the
modelinfo properties as importer.<property name>=...) and defaults are:
String catalog;
String schemaPattern;
String tableNamePattern;
String procedureNamePattern;
String[] tableTypes;
boolean useFullSchemaName = true; //when false the teiid name will be model.name
boolean importKeys = true;
boolean importIndexes = true;
boolean importApproximateIndexes = true;
boolean importProcedures = true;
JDBC Connector should be Metadata Aware Connector
-------------------------------------------------
Key: TEIID-687
URL:
https://jira.jboss.org/jira/browse/TEIID-687
Project: Teiid
Issue Type: Sub-task
Components: JDBC Connector
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Fix For: 6.2.0
Based on TEIID-685, JDBC Connector must implement this interface(s), so that any JDBC
sources can be used in dynamic data integration
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira