If Designer still has to create it's own connection to all these other data sources, which means maintaining all these other Connection Profiles.... then what's the real point of the Teiid Connection Importer? Wasn't it intended to help remove Designer's reliance on Connection Profiles and custom importers?

Provide hooks to interrogate metadata prior to full import ----------------------------------------------------------- Key: TEIID-3429 URL: https://issues.jboss.org/browse/TEIID-3429 Project: Teiid Issue Type: Feature Request Components: Server Reporter: Steven Hawkins Assignee: Steven Hawkins To support the Desinger we should offer the ability to interrogate metadata prior to full import. Exploring metadata is effectively an entirely different mode of operation with respect to the current metadata processing logic on the Teiid side. Also partial metadata isn't something that would neatly be expressed through DDL - tables without columns, a list of schema names, etc. Ways around that would be to expose source procedures for metadata interrogation: getTableNames - which would probably give both the Teiid name and the name in source and consider the current translator metadata settings getProcedureNames And importer specific info such as for JDBC getTableTypes, getCatalogNames, getSchemaNames I'd want to keep it fairly high level though. Getting column or key information I'd expect would be done through the normal full import.