[JBoss JIRA] (TEIIDDES-1918) JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ]
Mark Drilling commented on 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.
> 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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1924) Unable to edit the translator overridden property
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-1924:
-------------------------------------
Summary: Unable to edit the translator overridden property
Key: TEIIDDES-1924
URL: https://issues.jboss.org/browse/TEIIDDES-1924
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 8.3
Reporter: Van Halbert
Trying to edit the property (fix the name) in the translator override. However, when I clicked the 'edit' button, nothing happened. Couldn't edit the property name or couldn't decern that anything was editable.
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1922) Unable to deploy VDB due to requiring connection profile
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-1922:
-------------------------------------
Summary: Unable to deploy VDB due to requiring connection profile
Key: TEIIDDES-1922
URL: https://issues.jboss.org/browse/TEIIDDES-1922
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 8.3
Reporter: Van Halbert
Built a VDB to be used to query a JDG cache. However, can't deploy the VDB because there's no connection profile set. And unfortunately, there is not connection profile type for a JDG cache.
A person should be allowed to deploy the vdb, even though a connection profile is not setup, just provide a prompt to indicate which source doesn't have one, and continue.
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1921) Adding Translator-override, but doesn't like dash in name for type
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-1921:
-------------------------------------
Summary: Adding Translator-override, but doesn't like dash in name for type
Key: TEIIDDES-1921
URL: https://issues.jboss.org/browse/TEIIDDES-1921
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 8.3
Reporter: Van Halbert
When trying to add a translator override and enter the type, get an error message indicating the name is invalid. It says only letters, digits and dashes are valid. However, it didn't like the type name "infinispan-cache".
Note, this was done with no teiid server instance configured in Designer.
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1905) TrimColumn names should be enabled with hive translator metadata import
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1905?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1905:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1024875|https://bugzilla.redhat.com/show_bug.cgi?id=1024875] from ASSIGNED to MODIFIED
> TrimColumn names should be enabled with hive translator metadata import
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1905
> URL: https://issues.jboss.org/browse/TEIIDDES-1905
> Project: Teiid Designer
> Issue Type: Bug
> Environment: DV Beta
> Teiid Designer 8.3.Beta2
> Reporter: Filip Nguyen
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> *Problem*
> Importing Hive Tables, when using Teiid Connection >> Source model, is introducing padding spaces into column names.
> *Why*
> There is a problem with Hive 0.11 driver which introduces padding spaces into metadata (data types and column names). The problem has been resolved (TEIID-2524) but it is necessary that dynamic VDBs that import this metadata use importer property trimColumnNames property set to true. So it is probably needed to add this property to importVDB-vdb.xml in the case of hive translator import in the Designer.
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1911) Teiid Connection lacks a way to define importer properties
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1911?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1911:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1024875|https://bugzilla.redhat.com/show_bug.cgi?id=1024875] from ASSIGNED to MODIFIED
> Teiid Connection lacks a way to define importer properties
> ----------------------------------------------------------
>
> Key: TEIIDDES-1911
> URL: https://issues.jboss.org/browse/TEIIDDES-1911
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> In Teiid Connection importer, it lacks a way to define the "import" properties that makes usage cumbersome for user to define to import specific parts of schema, or sometimes impossible (see TEIID-1905)
> basically, when user chooses the "translator", after they should be able define some custom key/value pairs as properties, when then should be converted as model import properties in "importVDB-vdb.xml" file. Some sample properties are defined here
> https://docs.jboss.org/author/display/TEIID/JDBC+Translator
> see "importer" properties. Do not confuse similar "execution properties" which are translator overrides. The sample vdb is like this
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="hive" version="1">
> <description>Shows how to query HiveVDB using Hive</description>
> <property name="UseConnectorMetadata" value="cached"/>
> <model name="hive">
> <property name="importer.trimColumnNames" value="true"/>
> <source name="Hive conector" translator-name="hive" connection-jndi-name="java:/hive-ds"/>
> </model>
> </vdb>
> {code}
> As per GUI concerned it should be added in "Select the translator and target model" panel, after the selection of translator
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1905) TrimColumn names should be enabled with hive translator metadata import
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1905?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1905.
-------------------------------------
Resolution: Done
Resolved the related defect TEIIDDES-1911. With TEIIDDES-1911 changes, the user will now be able to pass a trim property in the importer.
> TrimColumn names should be enabled with hive translator metadata import
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1905
> URL: https://issues.jboss.org/browse/TEIIDDES-1905
> Project: Teiid Designer
> Issue Type: Bug
> Environment: DV Beta
> Teiid Designer 8.3.Beta2
> Reporter: Filip Nguyen
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> *Problem*
> Importing Hive Tables, when using Teiid Connection >> Source model, is introducing padding spaces into column names.
> *Why*
> There is a problem with Hive 0.11 driver which introduces padding spaces into metadata (data types and column names). The problem has been resolved (TEIID-2524) but it is necessary that dynamic VDBs that import this metadata use importer property trimColumnNames property set to true. So it is probably needed to add this property to importVDB-vdb.xml in the case of hive translator import in the Designer.
--
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
12 years, 5 months