[ https://issues.jboss.org/browse/TEIID-3429?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-3429: ------------------------------------- This feature was logged in response to 2 issues with Designer's Teiid Connection Importer: The primary issue is around the generic nature of the exposed *importer* properties. There have been a number of complaints about the performance of Designer trying to grab the DDL/Schema in the importer. In some cases just setting tableType == TABLE can drastically improve it. Our JDBC importer is a little smarter because we can get the table types, schema names and assist the user in fine-tuning the *requests* so we don't bring back ALL the metadata. * For the JDBC, what you offered in the description would be a great start. getTableTypes(), getCatalogNames(), getSchemaNames() would provide the user a shopping list to narrow down the import before calling getTableNames() and getProcedureNames(). A secondary issue is that some data source types are not supported through the importer. Flat File, XML File and Web Service (REST/SOAP) for instance. These require a conversation with the user to successfully model these sources. * Support for these other data sources would probably hinge on what schema/metadata is available to you, if at all. I would think that since our Flat File SQL, for instance, contains actual "data format" information that you don't really hold any schema for these file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)