[
https://issues.jboss.org/browse/TEIIDDES-1079?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1079:
----------------------------------------
Extracting models from a VDB feature is allowed via Quick Fix action contributed in
TEIIDDES-1611.
It's not a straight forward technique but does address some concerns above around
conflicting models in workspace. VDB validation now does provide some level of keeping
VDB's and workspace models in sync.
Create Import VDB wizard
------------------------
Key: TEIIDDES-1079
URL:
https://issues.jboss.org/browse/TEIIDDES-1079
Project: Teiid Designer
Issue Type: Sub-task
Components: Editors, Modeling, VDB & Execution
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Critical
Fix For: Future
For usability improvements and migration support, it would be great to be able to import
a VDB into a workspace, extract the models from the VDB into a new project (along with the
VDB) and allow the user to begin to start editing the models as if they were new.
Secondary thoughts:
- Should Translator Override properties be extractable from a VDB so users can apply them
to multiple VDB's?
- Then should the Translator Overrides action and editor be available in Teiid Designer
outside the VDB Editor??
- Should anything be done with Data Roles so they are transferable between VDB's?
- Do we need a Clone VDB action? which would clone the resources, vdb.xml contents, but
re-index the files?
- How do we handle extracting/importing models from VDB that already exist in the
workspace?
< First cut would maybe prevent user from extracting any models if any model
conflicts exist.
--
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