[
https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-2401:
----------------------------------------
So if a user is using * file,database, a git repo or combination of
all* for their artifact, are they using multiple tools to make this happen and what are
they?
In the Teiid code, the metadata repository is a pluggable concept. A user can
write their own metadata factory [repository]. Currently we have .INDEX(.vdb files), DDL,
NATIVE (reading from source) support.
And can these different tools actually talk to each other to discover
who/what tool is in charge of managing what metadata?
Explain why do you think they
need to discover and talk to each other? They each represent a metadata fragment in a VDB.
The vdb.xml file is one defining them together as one artifact.
Does each tool have a window or view into the contents of the deployed
artifact?
They are not tools, it is just metadata, they themselves represent the
views. When a user is writing a higher level metadata factory such as representing the
view model, they need to know what else is available, so that they can make use of it in
their transformations. That is where tools like Designer come in with nice GUI to make
them design that. However, Teiid will still do validation at the deployment time, what
they are referring to in their view transformations is in fact available and valid.
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)