November 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1917) Can't delete source model which imports VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1917?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1917: -------------------------------------- Assignee: Barry LaFond > Can't delete source model which imports VDB > ------------------------------------------- > > Key: TEIIDDES-1917 > URL: https://issues.jboss.org/browse/TEIIDDES-1917 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.3 > > > Source model that imports VDB can't be deleted. > Environment JBDS 7.0.0 GA > Tooling 4.1.3.Beta5 (http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...) > Steps to reproduce: > 1. Select File -> Import -> JDBC Database >> Source Model > 2. Create connection profile for VDB (Select Teiid as Connection profile type) > 3. Make sure that Import as VDB source model is checked > 4. Create the source Model > 5. Right-click on the source model and try to delete it, but Delete is inactive -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1917) Can't delete source model which imports VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1917?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1917: ----------------------------------- Fix Version/s: 8.3 > Can't delete source model which imports VDB > ------------------------------------------- > > Key: TEIIDDES-1917 > URL: https://issues.jboss.org/browse/TEIIDDES-1917 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.3 > Reporter: Van Halbert > Priority: Critical > Fix For: 8.3 > > > Source model that imports VDB can't be deleted. > Environment JBDS 7.0.0 GA > Tooling 4.1.3.Beta5 (http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...) > Steps to reproduce: > 1. Select File -> Import -> JDBC Database >> Source Model > 2. Create connection profile for VDB (Select Teiid as Connection profile type) > 3. Make sure that Import as VDB source model is checked > 4. Create the source Model > 5. Right-click on the source model and try to delete it, but Delete is inactive -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1918) JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1918: ----------------------------------- Priority: Critical (was: Major) > 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1918) JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1918: -------------------------------------- Assignee: Mark Drilling > 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 > > 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1918) JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1918: ----------------------------------- Fix Version/s: 8.3 > 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 > 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1887) Deploy and execute VDB throws exceptions if no server is defined

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1887?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1887. ------------------------------------- Fix Version/s: 8.3 Resolution: Done - added null checks at failure points from stacktraces. pull request: https://github.com/Teiid-Designer/teiid-designer/pull/255 > Deploy and execute VDB throws exceptions if no server is defined > ---------------------------------------------------------------- > > Key: TEIIDDES-1887 > URL: https://issues.jboss.org/browse/TEIIDDES-1887 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 8.2 > Environment: Teiid Designer 8.2.0.Final, JBDS 7.0.0.GA, jdk 1.7 > Reporter: Lucie Fabrikova > Assignee: Mark Drilling > Priority: Minor > Fix For: 8.3 > > > If no server is defined, deploy or execution of VDB causes an exception. > - rght click VDB: Modeling -> Deploy > Unhandled event loop exception > Caused by: java.lang.NullPointerException > at org.teiid.designer.runtime.ui.actions.DeployVdbAction.checkForConnectedServer(DeployVdbAction.java:221) > at org.teiid.designer.runtime.ui.actions.DeployVdbAction.run(DeployVdbAction.java:125) > - rght click VDB: Modeling -> Execute > java.lang.NullPointerException > at org.teiid.designer.runtime.ui.actions.ExecuteVDBAction.checkForConnectedServer(ExecuteVDBAction.java:127) > at org.teiid.designer.runtime.ui.actions.ExecuteVDBAction.run(ExecuteVDBAction.java:95) > - execute VDB via Guides view: > java.lang.NullPointerException > at org.teiid.designer.runtime.ui.vdb.ExecuteVdbAction.checkForConnectedServer(ExecuteVdbAction.java:88) > at org.teiid.designer.runtime.ui.vdb.ExecuteVdbAction.run(ExecuteVdbAction.java:60) > at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.executeAction(AdvisorActionFactory.java:556) > at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection.launchGuidesAction(TeiidGuidesSection.java:252) > at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection.access$1(TeiidGuidesSection.java:244) > at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection$3.doubleClick(TeiidGuidesSection.java:153) -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1913) Teiid Connection Importer should not proceed for some source types

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1913?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1913. ------------------------------------- Resolution: Done - now warns user they cannot proceed. pull request - https://github.com/Teiid-Designer/teiid-designer/pull/254 > Teiid Connection Importer should not proceed for some source types > ------------------------------------------------------------------ > > Key: TEIIDDES-1913 > URL: https://issues.jboss.org/browse/TEIIDDES-1913 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.3 > > > For some source types, teiid cannot generate DDL for creating the relational model - user is required to manually model. Two examples are ldap and mongodb. For these cases, the Teiid Connection importer should disallow their use - the vdb deployment and schema retrieval is not possible. > Need to determine which of the built-in drivers should be disallowed. If the user selects one of these types, show a message informing the user that manual modeling is required - and dont allow them to proceed. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1009) Improve Designer "Metadata from Text files on file system" import option

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1009: --------------------------------------------------- belong(a)redhat.com made a comment on [bug 780723|https://bugzilla.redhat.com/show_bug.cgi?id=780723] Since this was included in Beta release notes, I should probably make not of it in GA release notes. > Improve Designer "Metadata from Text files on file system" import option > ------------------------------------------------------------------------ > > Key: TEIIDDES-1009 > URL: https://issues.jboss.org/browse/TEIIDDES-1009 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: eds > Fix For: Future > > > Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc. > Also, change name to "Metadata from Flat or Text File" to distinguish it from "Metadata from Teiid Metadata File" -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1918) JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1918: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1026892|https://bugzilla.redhat.com/show_bug.cgi?id=1026892] from NEW to ASSIGNED > 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 > > 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1911) Teiid Connection lacks a way to define importer properties

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1911?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-1911: ------------------------------------- Assignee: Barry LaFond > 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 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > > 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2013