[
https://issues.jboss.org/browse/TEIID-3429?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3429:
---------------------------------------
I am asking how you are also externalizing the access to these
procedures?
All of the standard mechanisms would apply since they are nothing more than procedures.
Are you thinking something special, such as specific exposure on the adminapi?
BTW does SF provide any way interrogate metadata?
Not really that's why you'd only expose the getTables call, from there the user
could include/exclude for the final import which will be more time consuming as it needs
to pull all of the secondary metadata (keys, columns, etc.) - but that is much faster now
in any case with TEIID-3455. The Hive translator would act similarly.
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)