[teiid-issues] [JBoss JIRA] (TEIID-3429) Provide hooks to interrogate metadata prior to full import
[
https://issues.jboss.org/browse/TEIID-3429?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3429:
-------------------------------------
Are you thinking something special, such as specific exposure on the
adminapi?
I guess, you are thinking to expose as procedures, then they can be called using the jdbc
interface. My concern there is there is two ways we providing the exposure to the source
metadata, one through "getSchema" method on admin API and through JDBC. It would
be nice to provide single way.
Yes, without that tools like designer will not have access to raw metadata. Also this
needs to be on empty (vdb with metadata not loaded based on some flag, except for methods
you mentioned above) vdb, which is pre-cursor to when you are ready to do the import with
full "importer" properties that can get the actual metadata.
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)