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

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

> I do not think I follow you on this one. there is no execute-query on admin?

It's not exposed on the AdminApi interface, but there is an execute-query operation.

>  I am failing to see is, how this metadata access is different from current SYS tables. (I know content is different, I am asking about the interface)

The content is entirely different.  The sys tables are derived from the loaded metadata.  There would be no loaded metadata for translator metadata procedures - it's just a minimal re-exposure of their metadata facilities.  I'm proposing very little magic or abstraction - the import process will still need knowledge of a flow (ask for catalog and table types first, then schemas, then tables/procedures).  The interface is entirely different as well.  These would be source procedures vs. system tables.

> I do like you Admin suggestion without vdb.There may be merits for both, but if this is primarily for tooling, I am somehow blocked in my thinking past the Admin 

This doesn't fit neatly with any existing concept as you're not really dealing with a proper vdb nor the Teiid metadata.  Most generically an admin method could be:

List<List<?>> getMetadata('metadata method', List of args, 'translator name', Map of translator properties, 'jndi name').  However if we are going that far, then it may be just as well to not route this logic through the translator at all and just introduce some light weight remoting logic such that the Designer can get at the metadata facilities of the relevant connection directly.

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