[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=13064519#comment-13064519 ] 

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

The code I have will add a special flag to the salesforce and the jdbc translators - something like exposeMetadata.  Then on the getMetadata call instead of calling the normal MetadataProcessor logic, we'll expose procedures to assist with import.  For JDBC this would be:

getTableTypes, getCatalogs, getSchemas, getTables, and getProcedures - with result sets that are similar to the analogous DatabaseMetadata methods.  These would strictly be for examining the source metadata and would not use any import properties.

For salesforce we would just have getTables.

After interrogating those methods, Designer would set the appropriate importer values and deploy a vdb to perform the full import and produce the DDL.

Any thoughts?

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