[ https://issues.jboss.org/browse/TEIID-3429?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3429: --------------------------------------- Any interface yes. Even the execute-query admin operation. A couple of things. First is that DDL is not appropriate for this. As mentioned in the description it doesn't make sense to send back partial DDL. The next is that it seems clearer to expose the source view of metadata rather than the Teiid view - as that is more idiomatic to the import process. So these procedures would return values that represent source structure - source table name, schema, and catalog for jdbc rather than just a name in source. Lastly the admin logic is somewhat of a one off - there's a lot more overhead in adding new handlers, support (or not) for embedded, etc. The only benefit I can see from using the admin would be to deploy the vdb with connection type none such that it's not generally accessible. Alternatively over admin you could have something that takes a translator name, a jndi name, translator properties, etc. to not require a vdb. Just to make sure I'm not missing something, are you simply reiterating or do want to see something different about this flow? -- This message was sent by Atlassian JIRA (v6.3.15#6346)