[teiid-issues] [JBoss JIRA] (TEIID-3429) Provide hooks to interrogate metadata prior to full import

[Barry LaFond (JIRA)]

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

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.




> 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)