[
https://issues.jboss.org/browse/TEIIDDES-1478?page=com.atlassian.jira.plu...
]
Barry LaFond resolved TEIIDDES-1478.
------------------------------------
Release Notes Text: The JDBC importer detects if the Connection Profile is of a Teiid
VDB connection type. If so, then the user has the default option to create a VDB Source
Model for a single schema within that VDB. The name of the VDB Source model is determined
by the schema name in the VDB (aka model name) and the resulting VDB source model will be
treated as Read-Only
Resolution: Done
The JDBC importer detects if the Connection Profile is of a Teiid VDB connection type. If
so, then the user has the default option to create a VDB Source Model for a single schema
within that VDB. The name of the VDB Source model is determined by the schema name in the
VDB (aka model name) and the resulting VDB source model will be treated as Read-Only
Modify JDBC import relational processor to tag model as a VDB source
model
--------------------------------------------------------------------------
Key: TEIIDDES-1478
URL:
https://issues.jboss.org/browse/TEIIDDES-1478
Project: Teiid Designer
Issue Type: Sub-task
Components: Import/Export, Modeling
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Blocker
Fix For: 8.0
Modify the JDBC import processor to identify connection is a Teiid VDB source, then
inject appropriate tags/extension info into the model to identify it as a VDB Source
Model.
*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)
--
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