Bug 1026892
| Summary: | JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Filip Elias <felias> |
| Component: | Tooling | Assignee: | Van Halbert <vhalbert> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | atangrin, ldimaggi, ncross, vhalbert |
| Target Milestone: | CR1 | ||
| Target Release: | 6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
If using the loopback VDB to import a VDB as a data source to another, and the imported VDB contains table with column of type integer, then a validation error is presented to the user.
|
Story Points: | --- |
| Clone Of: | Environment: |
JBDS 7.0.0 GA
Tooling 4.1.3.Beta5 (http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.3.Beta5/)
|
|
| Last Closed: | 2014-02-06 15:37:10 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Mark Drilling <mdrilling> made a comment on jira TEIIDDES-1918 I ran into a couple problems with the scenario (from Designer). Maybe I'm doing something wrong... 1) Steps 1-3. I created a Model with one table and two columns. Then created a VDB, added the Model, set the translator to 'loopback'. I could not deploy/execute the VDB from Designer. It requires a CP to be set, but there is no CP. Then I manually copied the VDB to the server deployments folder, then was able to query it. 2) I couldnt complete steps 3.1-3.3. The last page of the importer would not let me specify a new model. Step 3.1 says "Import as VDB source model" has be be checked, but I had to uncheck it. 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. Mark Drilling <mdrilling> made a comment on jira TEIIDDES-1918 I see where the type mismatch is ocurring. Will discuss potential fix with Barry tomorrow. Also need to go thru a couple 'VDB source model' scenarios with him. Mark Drilling <mdrilling> updated the status of jira TEIIDDES-1918 to Resolved Mark Drilling <mdrilling> made a comment on jira TEIIDDES-1918 Resolved type mismatch issue pull request - https://github.com/Teiid-Designer/teiid-designer/pull/259 Verified on DV6 CR1, JBDS 7.1.0, JBDS IS 7.0.0.CR1 Barry LaFond <blafond> updated the status of jira TEIIDDES-1918 to Closed |
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