[
https://issues.jboss.org/browse/TEIID-4807?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4807:
---------------------------------------
Even with the xml format, get-schema always returned the schema not
import information, this enhancement just expanded to whole vdb.
That is not correct, it's not a consistent output. If you specify XML, you'll
effectively get the vdb.xml with extra schema information. If you specify ddl, you
won't get the schema information, but not the full equivalent of the vdb.xml or
vdb.ddl.
IMO these utilities are important to get users converted over to
using DDL
Which is important that we offer something that is a full representation. If we move
fully in the direction of undoing our notion of metadata management in favor of an online
metadata system, then this
DDL format of a vdb lacks import information
--------------------------------------------
Key: TEIID-4807
URL:
https://issues.jboss.org/browse/TEIID-4807
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.3, 9.2.1
Database and schema imports are not represented from the admin getSchema logic. It looks
better that we still restrict this to just a schema for now.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)