[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-1403) Add a vdb reuse feature
[
https://issues.jboss.org/browse/TEIIDDES-1403?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1403:
----------------------------------------
Turns out that creating 1 VDB source model containing multiple "schema/models"
won't work.
Teiid runtime/query structure dictates that the re-use vdb components be separate
relational models accessible in a user's workspace.
1) Create action/concept of "Create/Export a re-use VDB"
* Option 1: create models defined in 2) below in some folder location
* Option 2: create models but place in transportable "zip" file?
2) this VDB, would take the form of a set of one or more models defined by a vdb
(remote/deployed or LOCAL)
* These models would still have the "vdb-name" and "locked" extension
property in them.
* VDB Editor (VdbModelEntry.synch()) would still detect these models and add
"import-vdb" entries.
3) These models would be stored in a separate container/folder (preferably a different
model project)
* Maybe provide a property for user defining a single "VDB Reuse" project or
designated folder location
* For the use-case of using a "local vdb" as the imported vdb we need a way to
prevent duplicate model name (schema) problems in transformations
Add a vdb reuse feature
-----------------------
Key: TEIIDDES-1403
URL: https://issues.jboss.org/browse/TEIIDDES-1403
Project: Teiid Designer
Issue Type: Feature Request
Components: Teiid Integration, VDB & Execution
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Dan Florian
Fix For: 8.0
See https://issues.jboss.org/browse/TEIID-1366, which not only replaces mergeVDB
functionality, but provides a declarative way for vdbs to be reused at runtime. Designer
will need to provide a representation of the reuse feature that includes:
- Optionally an artifact that represents a vdb to import, but that only contains the
consumable metadata - _not the transformations_.
- A way to manage those imported artifacts in the context of a workspace
- A way to edit the imports in the vdb.xml to specify the name/version of what's
expected at runtime
- preview would be broken unless a deployed version the re-use VDB existed
An expected flow should be available from GSS customer requests and at a high-level could
be described as:
*Scenario A*
* Team 1 develops a vdb and exports the "*reuse* *vdb*" _without_
_transformation_ _metadata_ for use by Team 2
* Team 2 develops a new vdb using the reuse vdb - no access is needed to the original
vdb
*Scenario B*
* Team 1 develops a vdb and provides it directly to Team 2
* Team 2 uses original vdb as "source" and models new vdb from it
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira