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

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

> For (2) you will be developing a new MetadataFactory that understands the translator level "getCatalog" kind methods. or modify the DDL Metadata Factory to do the same with help of some flag. 

Neither.  Again I don't think this metadata task fits well with our current MetadataFactory/MetadataProcessor logic.  Instead it's the translator that is exposing procedures that provide access to underlying metadata facilities.  The only thing that we may need to do on top of that is to expose the potential runtime name for using include/exclude.

> I thought using both JDBC and Admin interfaces for what looks like single task for user prespective is not good. Other than that I do not have any other objections

Again unless we want to have this done in a vdb-less way, I don't see much advantage of using the admin interface.

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