1:25 p.m.
[
https://issues.jboss.org/browse/TEIIDDES-1403?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1403:
----------------------------------------
Based on all the input so far, this will be our initial implementation of VDB Re-use in
Designer.
1) Create JDBC Importer option for Teiid-only connections
* During import, user can select/deselect schema (models) and tables on Select Database
Objects page
* Add Check-box for "Import as VDB Source Model" to Specify Import Options page
** Add "description" to note that this is a Teiid VDB import and can be treated
in a special way.
*** Maybe we default the checkbox to CHECKED?
** if checked, then disable other options
*** Make target a view model (DISABLE as UNCHECKED)
*** Include catalog for Fully Qualified Names (DISABLE as UNCHECKED)
*** Use Fully Qualified Names (DISABLE as CHECKED)
**** schema serves as original Model Name and is required for query validation
*** Change Case for All Characters (DISABLE as UNCHECKED)
2) Create/Modify JDBC Import Processor
* Add VDB name and version as extension data to Model Annotation
** Need to be aware of this new extension data on MS sequencing?
* Create VdbSourceModelExtensionHandler class that can peek into ModelResource/IFile and
check to see if it's a VDB Source Model as well as inject extension data (See use of
ResourceAnnotationHelper class for connection info)
4) VDB Editor changes
* Modify VDBModelEntry to look for dependent models, check for
'isVdbSourceModel()" and NOT add index files.
** Add option to "add XMI files" anyway?
* Show VDB Source models "differently"
** Show VDB Import as a different VdbModelEntry? (source model icon with yellow VDB on
it?)
5) Add any new validation rules
6) Look at potential for circular dependencies?
* Create VdbSourceModelAnalyzer
* Able to view Tables and table names + VDB name to create a "VDB perspective"
of contents?
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira