[ https://issues.jboss.org/browse/TEIID-3429?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3429: --------------------------------------- It's not exposed on the AdminApi interface, but there is an execute-query operation. 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. 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346)