[
https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu...
]
RH Bugzilla Integration commented on TEIIDDES-1918:
---------------------------------------------------
Filip Elias <felias(a)redhat.com> made a comment on [bug
1026892|https://bugzilla.redhat.com/show_bug.cgi?id=1026892]
Hello Mark,
1) You have to choose any JNDI Name (in the Source Binding Definition ) from the list.
Then you should be able to deploy loopback VDB.
2) Do you create the importing VDB in the different Teiid Model Project? Otherwise the
model name collides with the model name of the loopback VDB and can't be changed.
JDBC importer adds wrong column type for columns of type integer,
when importing(Reusing) VDB
----------------------------------------------------------------------------------------------
Key: TEIIDDES-1918
URL:
https://issues.jboss.org/browse/TEIIDDES-1918
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.3
Reporter: Van Halbert
Assignee: Mark Drilling
Priority: Critical
Fix For: 8.3
When a VDB is imported(reused) by another VDB and the imported VDB contains table with
column of type integer, then the importing VDB will throw validation error.
Steps to reproduce:
1. Create loopback VDB, add table DATA with two columns, one of type integer and one of
the string
2. Deploy the loopback VDB
3. Reuse the looback VDB
3.1. Import the loopback VDB through JDBC importer
"Import as VDB source model" have to be checked
3.2 Create view model, use table DATA in the view model
3.3 Create and deploy new VDB
When deploying the VDB, error occures:
TEIID31080 View data validation error: QueryValidatorException-The definition for data
has the wrong type for column 1. Expected bigdecimal, but was biginteger.
15:57:48,718 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40073 The metadata
for the VDB aaa.1 is loaded, however it is not valid. Check models for errors. Correct the
metadata and re-deploy.
15:57:48,719 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40003 VDB aaa.1 is
set to FAILED
--
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