[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 edited comment on TEIIDDES-1403 at 8/9/12 4:07 PM:
----------------------------------------------------------------
Seems like the use-case in the description is pretty limited and it also requires Designer
to create/manage a new artifact type, "reuse VDB"
I would think that users would most likely want to continue to do all modelling in their
workspace, including modelling sources and views, creating source and view VDBs and
utilizing VDBs as sources (reuse VDBs)
Would also suggest adding a requirement that we expose model visibility as well data role
security/info in the solution. Is Teiid equipped in 8.x to handle adhering to the values
in the dependent VDBs?
was (Author: blafond):
Seems like the use-case in the description is pretty limited and it also requires
Designer to create/manage a new artifact type, "reuse VDB"
I would think that users would most likely want to continue to do all modelling in their
workspace, including modelling sources and views, creating source and view VDBs and
utilizing VDBs as sources (reuse VDBs)
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: 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
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