[
https://issues.jboss.org/browse/TEIIDDES-3059?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-3059:
----------------------------------------
With 9.3 Teiid will also support a .vdb archive with following contents
/META-INF
vdb.ddl
model-one-schema.ddl
model-two-schema.ddl
..
..
Where in "model-one-schema.ddl" and "model-two-schema.ddl" files
contain DDL for a specific schema defined in the vdb.ddl file. This file is imported using
a statement
{code}
IMPORT FOREIGN SCHEMA '%' FROM REPOSITORY "DDL-FILE" INTO my-model-one
OPTIONS("ddl-file" '/model-one-schema.ddl')
IMPORT FOREIGN SCHEMA '%' FROM REPOSITORY "DDL-FILE" INTO my-model-two
OPTIONS("ddl-file" '/model-two-schema.ddl')
{code}
DDL file can contain either physical or virtual models. For more information full
semantics of DDL, please see Teiid documentation.
Allow support for vdb.ddl in the .vdb files
-------------------------------------------
Key: TEIIDDES-3059
URL:
https://issues.jboss.org/browse/TEIIDDES-3059
Project: Teiid Designer
Issue Type: Enhancement
Components: Teiid Integration, VDB & Execution
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
With the DDL based metadata, ".vdb" file archive should allow to contain a
"vdb.ddl" file that can be deployed. Based on TEIID-4719 this needs to allow to
load metadata from INDEX and DDL-FILE metadata repositories.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)