[
https://issues.jboss.org/browse/TEIIDDES-1403?page=com.atlassian.jira.plu...
]
Barry LaFond edited comment on TEIIDDES-1403 at 8/6/12 5:01 PM:
----------------------------------------------------------------
Issues include
* extracting table/view/column metadata from VDB containing Source and View Models
* How does Designer use this metadata in the current Transormation framework
* Tracking and injecting VDB imports into workspace VDBs at design-time
Possible solution:
* Export Metadata (DDL ?) from a VDB and convert to a Foreign Source Model containing some
new relational extension data
* EXAMPLE: isForeignModel == TRUE , vdbName == "employeesVDB"
* Foreign Source Models would have to maintain some original PATH information
* Foreign Source Models would have to include actual View/Table/Column UUID's
* when that source model is added to a VDB, the vdb import would be created and that
Foreign Source model NOT added to VDB
was (Author: blafond):
Issues include
* extracting table/view/column metadata from VDB containing Source and View Models
* How does Designer use this metadata in the current Transormation framework
* Tracking and injecting VDB imports into workspace VDBs at design-time
Possible solution:
* Export Metadata (DDL ?) from a VDB and convert to a Foreign Source Model containing some
new relational extension data
* EXAMPLE: isForeignModel == TRUE , vdbName == "employeesVDB"
* when that source model is added to a VDB, the vdb import would be created and that
Foreign Source model NOT added to VDB
Add a vdb reuse feature
-----------------------
Key: TEIIDDES-1403
URL:
https://issues.jboss.org/browse/TEIIDDES-1403
Project: Teiid Designer
Issue Type: Sub-task
Components: Teiid Integration, VDB & Execution
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Paul Richardson
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
An expected flow should be available from GSS customer requests and at a high-level could
be described as:
Team 1 develops a vdb and exports the "reuse vdb" without transformation
metadata for use by Team 2
or Team 1 develops a vdb and provides it directly to Team 2
Team 2 develops a new vdb using the reuse vdb - no access is needed to the original vdb
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira