[
https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2401:
----------------------------------------
In debug, I intercepted the getSchema() method via the Teiid importer and verified that if
I give it deployed VDB name, it can return virtual table DDL for a view model.
So, my next question is.... wouldn't it be fairly straight forward to
"export" a VDB.vdb as a dynamic VDB? I.e. Teiid runtime does the conversion?
All the metadata is already on the server side, (including the -vdb.xml maniffest) and the
methods to convert the metadata into DDL already work. All that's left is to inject
the DDL into the VDB XML and the conversion is done? If we're going to require the
user to Deploy a VDB anyway in order to create a dynamic VDB version of it, seems like the
utility makes more sense as part of the API.
maybe something like: *String getDynamicVdb(String vdbName, int version, String[]
modelNames, EnumSet<SchemaObjectType> allowedTypes, String typeNamePattern));*
Designer would wrap this as maybe an *Convert to Dynamic VDB* action for a deployed VDB
(server view/wizard) or via an action in the workspace that would/could temporarily
auto-deploy a VDB, do the import/conversion, then undeploy the VDB.
Being on the server-side, users could also programattically convert/export EMF VDB's
to dynamic VDBs. Openshift would also benefit if users were going to migrate in the
future.
Add support exporting the Designer VDB as Dynamic VDB
-----------------------------------------------------
Key: TEIIDDES-2401
URL:
https://issues.jboss.org/browse/TEIIDDES-2401
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Reporter: Ramesh Reddy
When a VDB is developed in the Designer, provide an option to export the given VDB as
Dynamic VDB, which is simple XML format using DDL.
The server already provides mechanism to retrieve the schema (DDL) for a given model.
Using this technique of retrieving the DDL, this feature can be built.
One caveat is support for XML document models in Dynamic VDB. When VDB contains XML
document model, do not support this feature.
This has couple benefits
* Users can use these in Teiid for simplified usage.
* Can used to check the models into source repository like GIT or SVN etc and compare
with later versions for modifications
* Open Shift
As for importing of Dynamic VDB, that can be handled as separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)