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

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-3429:
---------------------------------------

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

Thus the question about whether we want to more aggressively set default or make the user fill in more prior to importing.

> These require a conversation with the user to successfully model these sources.

Yes and that would still be the case even with these changes as they would only offer be effective for JDBC, Hive, and Salesforce.

As I see it the approaches are:

1. have Teiid re-expose source metadata as exposed above
2. continue to have Designer interact with a local source Connection, for metadata interrogation purposes, then perform the final import with the server.

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