[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:
-------------------------------------
Any interface yes. Even the execute-query admin operation.
I do
not think I follow you on this one. there is no execute-query on admin?
do want to see something different about this flow?
Yes, was
re-iterating for implementation purpose.
I see that, you are looking at this as way to expose the these methods on generically on a
translator, which is not related to metadata load process at all. More like exposing
system tables for sources, but through procedures. They will serve the data from directly
from source, rather then already loaded metadata for that model. 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)
I am thinking more of flow to build up the query to load metadata for model, thus I see it
as exposing as Admin method. 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 :(
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)