February 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1822) Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1822?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1822: ---------------------------------------- Need to do more work on use-cases before attempting to implement this change. Pushing to 8.5 > Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1822 > URL: https://issues.jboss.org/browse/TEIIDDES-1822 > Project: Teiid Designer > Issue Type: Task > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.4 > > > 1) Set-up simple JDBC source/model/vdb and test/execute VDB > 2) Delete the Data Source in the Server view > 3) Try and execute the VDB again and get exception logged in console > Seems the active/inactive status is old terminology and Designer should be using the isActive() call as well as getValidityErrors() to fine-tune the state of a VDB and prevent Execute VDB from being launched or at least a warning message check. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1822) Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1822?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1822: ----------------------------------- Fix Version/s: 8.5 (was: 8.4) > Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1822 > URL: https://issues.jboss.org/browse/TEIIDDES-1822 > Project: Teiid Designer > Issue Type: Task > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.5 > > > 1) Set-up simple JDBC source/model/vdb and test/execute VDB > 2) Delete the Data Source in the Server view > 3) Try and execute the VDB again and get exception logged in console > Seems the active/inactive status is old terminology and Designer should be using the isActive() call as well as getValidityErrors() to fine-tune the state of a VDB and prevent Execute VDB from being launched or at least a warning message check. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1657) Update and publish E2E Yahoo UDF Test Script as wiki document

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1657?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1657: ----------------------------------- Fix Version/s: 8.5 (was: 8.4) > Update and publish E2E Yahoo UDF Test Script as wiki document > ------------------------------------------------------------- > > Key: TEIIDDES-1657 > URL: https://issues.jboss.org/browse/TEIIDDES-1657 > Project: Teiid Designer > Issue Type: Sub-task > Components: Documentation > Reporter: Barry LaFond > Fix For: 8.5 > > Attachments: TestUDF.jar, translator-yahoo-7.1.0.jar > > > The E2E Yahoo UDF Test Script involves helping users understand and work with a custom translator as well as a User Defined Function. > Develop a Wiki article that walks a user through the setup, modeling and testing of this use-case. > Attached is the custom translator jar and the custom UDF jar. > Note for 8.3, the notion of UDF's are now confined to View models. See TEIIDDES-1973 and TEIIDDES-1974 for changes and tweak the E2E script to reflect these changes. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1987) Add BIRT plugin dependencies to force adding their MongoDB and HIVE connection profiles to Designer build

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1987?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1987: ----------------------------------- Fix Version/s: 8.5 (was: 8.4) > Add BIRT plugin dependencies to force adding their MongoDB and HIVE connection profiles to Designer build > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1987 > URL: https://issues.jboss.org/browse/TEIIDDES-1987 > Project: Teiid Designer > Issue Type: Task > Components: Build, Datatools Integration > Affects Versions: 8.3 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.5 > > > Designer 8.3 introduced MongoDB extension properties to allow defining MongoDB relational models. The BIRT project contributes MongoDB and HIVE connection profile wizards and DTP explorer functionality that would be beneficial for users to test and import/construction their Designer models. > Find a way to add BIRT dependency to at a minimum, include the plugins that contribute these connection profiles. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1126) Add Wizard to Build "XSD to Relational" and "Relational to XSD" Procedures

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1126?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1126: ----------------------------------- Fix Version/s: 8.5 (was: 8.4) > Add Wizard to Build "XSD to Relational" and "Relational to XSD" Procedures > --------------------------------------------------------------------------- > > Key: TEIIDDES-1126 > URL: https://issues.jboss.org/browse/TEIIDDES-1126 > Project: Teiid Designer > Issue Type: Enhancement > Components: Transformations > Affects Versions: 7.5 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.5 > > > Need a wizard to select model, procedure name, and schema elements to build procedures for "XML to Scalar" and "Scalar to XML" -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2041) Null Pointer Exception creating DB2 JDBC Connection

by Jim Riley (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2041?page=com.atlassian.jira.plu... ] Jim Riley commented on TEIIDDES-2041: ------------------------------------- I really don't know where Teiid Designer stops and eclipse starts. So it could be an eclipse Issue. My steps were to open Teiid Designer. Under the Guides Panel --> Action Sets --> Model JDBC Source I selected "Create JDBC connection". A "New Connection Profile" is displayed and I selected "Generic JDBC". On the next panel I picked the driver that I setup. That profile included the DB2 net driver jar and license jar: "db2jcc.jar" and "db2jcc_license_cisuz.jar" using the driver class "com.ibm.db2.jcc.DB2Driver". Since you used db2jcc4.jar, I added another profile using "db2jcc4.jar" and "db2jcc_license_cisuz.jar". (FYI, Both configurations successfully work with SQLSquirrel and RAD). The comparing the results, the problem appears consistent: Could not connect to DMS. Error creating SQL Model Connection connection to DMS. (Error: null) java.lang.NullPointerException OK !MESSAGE Error creating SQL Model Connection connection to DMS. (Error: null) !STACK 0 java.lang.NullPointerException at org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.getCatalogDatabase(DatabaseProviderHelper.java:37) at org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.setDatabase(DatabaseProviderHelper.java:47) at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.initializeJDBCConnection(ConnectionInfoImpl.java:718) at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.<init>(ConnectionInfoImpl.java:690) at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:38) at org.eclipse.datatools.connectivity.sqm.core.SQMConnectionFactory.createConnection(SQMConnectionFactory.java:45) at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:59) at org.eclipse.datatools.connectivity.internal.ConnectionFactoryAdapterProvider.createConnection(ConnectionFactoryAdapterProvider.java:114) at org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(ManagedConnection.java:163) at org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !SUBENTRY 1 unknown 0 0 2014-02-07 09:35:13. I did not mention, the database I am connection to is "DB2 v9.5.0.3" hosted on AIX. Changing to the Database Development perspective, it produces the same error when I try to connect. Using the Database Development perspective in RAD, I connect successfully. The two environments differ. Most noticeably, (1) the base versions of eclipse differ and (2) One uses IBMs JVM and for Teiid I used Oracle's 1.7. > Null Pointer Exception creating DB2 JDBC Connection > --------------------------------------------------- > > Key: TEIIDDES-2041 > URL: https://issues.jboss.org/browse/TEIIDDES-2041 > Project: Teiid Designer > Issue Type: Bug > Environment: Designer 8.3.1.Final-v20140122-1920-B21. Running in eclipse Kepler on Windows 7 with jdk1.7.0_45 > Reporter: Jim Riley > > When trying to Make a JDBC connection to DB2 Database a Null Pointer Exception is encountered. The Ping to test the connection is successful. > I tried connecting to a AIX DB2 instance and a Mainframe instance. The result was the same. > The detailed messages is: > Could not connect to New Generic JDBC. > Error creating SQL Model Connection connection to New Generic JDBC. (Error: null) > java.lang.NullPointerException > OK > The log file contains: > !ENTRY org.eclipse.datatools.connectivity 4 -1 2014-02-06 10:18:14.869 > !MESSAGE Could not connect to DMS Net Driver JDBC. > !SUBENTRY 1 org.eclipse.datatools.connectivity 4 -1 2014-02-06 10:18:14.869 > !MESSAGE Error creating SQL Model Connection connection to DMS Net Driver JDBC. (Error: null) > !STACK 0 > java.lang.NullPointerException > at org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.getCatalogDatabase(DatabaseProviderHelper.java:37) > at org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.setDatabase(DatabaseProviderHelper.java:47) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.initializeJDBCConnection(ConnectionInfoImpl.java:718) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.<init>(ConnectionInfoImpl.java:690) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:38) > at org.eclipse.datatools.connectivity.sqm.core.SQMConnectionFactory.createConnection(SQMConnectionFactory.java:45) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:59) > at org.eclipse.datatools.connectivity.internal.ConnectionFactoryAdapterProvider.createConnection(ConnectionFactoryAdapterProvider.java:114) > at org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(ManagedConnection.java:163) > at org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > !SUBENTRY 1 unknown 0 0 2014-02-06 10:18:14.869 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1843) could installation of Teiid Designer be made simpler via p2 metadata <references> to upstream sites?

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1843?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-1843: ------------------------------------ Fix Version/s: 8.5 (was: 8.4) Per Barry, pushing to 8.5 release > could installation of Teiid Designer be made simpler via p2 metadata <references> to upstream sites? > ---------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1843 > URL: https://issues.jboss.org/browse/TEIIDDES-1843 > Project: Teiid Designer > Issue Type: Bug > Components: Build, Documentation, Usability > Affects Versions: 8.2 > Reporter: Nick Boldt > Assignee: Mark Drilling > Fix For: 8.5 > > Attachments: InstallError.png, TEIIDDES1843.png, TEIIDDES1843_2.png > > > Current instructions for installing Teiid Designer 8.2 [1] involve multiple steps, installs, and restarts of Eclipse. This is more complex than it needs to be. > [1] https://www.jboss.org/teiiddesigner/downloads > Instead, the Teiid Designer update site could simply reference the upstream URLs that it needs to perform the installation, and as long as all of Teiid Designer's features & plugins properly define dependencies on the required upstream features and plugins on these update sites, installation should be able to proceed from a single URL, rather than a handful. It would allow installation via a single step, rather than several iterative steps. > I'll attach a PR to demonstrate this. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1843) could installation of Teiid Designer be made simpler via p2 metadata <references> to upstream sites?

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1843?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-1843: ------------------------------------ Attachment: InstallError.png > could installation of Teiid Designer be made simpler via p2 metadata <references> to upstream sites? > ---------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1843 > URL: https://issues.jboss.org/browse/TEIIDDES-1843 > Project: Teiid Designer > Issue Type: Bug > Components: Build, Documentation, Usability > Affects Versions: 8.2 > Reporter: Nick Boldt > Assignee: Mark Drilling > Fix For: 8.4 > > Attachments: InstallError.png, TEIIDDES1843.png, TEIIDDES1843_2.png > > > Current instructions for installing Teiid Designer 8.2 [1] involve multiple steps, installs, and restarts of Eclipse. This is more complex than it needs to be. > [1] https://www.jboss.org/teiiddesigner/downloads > Instead, the Teiid Designer update site could simply reference the upstream URLs that it needs to perform the installation, and as long as all of Teiid Designer's features & plugins properly define dependencies on the required upstream features and plugins on these update sites, installation should be able to proceed from a single URL, rather than a handful. It would allow installation via a single step, rather than several iterative steps. > I'll attach a PR to demonstrate this. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1843) could installation of Teiid Designer be made simpler via p2 metadata <references> to upstream sites?

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1843?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1843: ----------------------------------------- I overlooked this in my inbox. In the previous comment, Paul is saying that steps 2 and 3 can be removed from the install instructions page I tried the installation without those steps and I'm still getting dependency error - see attached screenshot. > could installation of Teiid Designer be made simpler via p2 metadata <references> to upstream sites? > ---------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1843 > URL: https://issues.jboss.org/browse/TEIIDDES-1843 > Project: Teiid Designer > Issue Type: Bug > Components: Build, Documentation, Usability > Affects Versions: 8.2 > Reporter: Nick Boldt > Assignee: Mark Drilling > Fix For: 8.4 > > Attachments: TEIIDDES1843.png, TEIIDDES1843_2.png > > > Current instructions for installing Teiid Designer 8.2 [1] involve multiple steps, installs, and restarts of Eclipse. This is more complex than it needs to be. > [1] https://www.jboss.org/teiiddesigner/downloads > Instead, the Teiid Designer update site could simply reference the upstream URLs that it needs to perform the installation, and as long as all of Teiid Designer's features & plugins properly define dependencies on the required upstream features and plugins on these update sites, installation should be able to proceed from a single URL, rather than a handful. It would allow installation via a single step, rather than several iterative steps. > I'll attach a PR to demonstrate this. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1901) Teiid Connection Importer is using the pool-name instead of jndi name

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1901?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1901. ------------------------------------- Resolution: Done jndi names were added on the first page of the TeiidConnection Importer wizard. also on the Server View datasource nodes. pull request: https://github.com/Teiid-Designer/teiid-designer/pull/286 > Teiid Connection Importer is using the pool-name instead of jndi name > --------------------------------------------------------------------- > > Key: TEIIDDES-1901 > URL: https://issues.jboss.org/browse/TEIIDDES-1901 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Fix For: 8.3.2, 8.3 > > > When using the "Teiid Connection" importer the data sources are identified with "pool-name" rather than the "jndi" name. -- 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, 2 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 February 2014