[
https://issues.jboss.org/browse/TEIIDDES-2828?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2828:
----------------------------------------
Importing Models from a deployed VDB via JDBC does not provide the ability to discover the
VDB version from the JDBC metadata.
Since the JDBC importer *is* aware that the source is a VDB, we could provide a text entry
field to allow users to set the version, which would be stored in the model along with the
"import-vdb" name. Then on *preview*, we would set the proper VDB version
number.
VDBs, created with Teiid Designer that import other VDB do not
respect the specified version.
---------------------------------------------------------------------------------------------
Key: TEIIDDES-2828
URL:
https://issues.jboss.org/browse/TEIIDDES-2828
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 9.0.6
Reporter: Colin Mondesir
Assignee: Barry LaFond
Fix For: 10.0.2
When using:
project -> Import...
JDBC Database >> Source Model,
Despite including the URL property VirtualDatabaseVersion=2 during the import process the
version of the imported vdb I see when I create a deployable vdb archive is given as
"1":
...
<import-vdb name="fileData" version="1"
import-data-policies="false"/>
As an alternative I have tried setting the "version" property given here:
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Virtuali...
But saw the same results the version of my imported VDB always seems to be "1"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)