January 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-910) Convert the Admin API implemention based on Profile Service

by Ramesh Reddy (JIRA)

Convert the Admin API implemention based on Profile Service ----------------------------------------------------------- Key: TEIID-910 URL: https://jira.jboss.org/jira/browse/TEIID-910 Project: Teiid Issue Type: Sub-task Reporter: Ramesh Reddy Assignee: Ramesh Reddy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-938) MySql queries pushed down to the source producing error: Invalid conversion from type class com.metamatrix.common.types.BlobType with value 'javax.sql.rowset.serial.SerialBlob@1b1395dc' to type class java.lang.Character

by Warren Gibson (JIRA)

MySql queries pushed down to the source producing error: Invalid conversion from type class com.metamatrix.common.types.BlobType with value 'javax.sql.rowset.serial.SerialBlob@1b1395dc' to type class java.lang.Character ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-938 URL: https://jira.jboss.org/jira/browse/TEIID-938 Project: Teiid Issue Type: Thirdparty Change Components: Query Engine Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Steven Hawkins Approximately 20 queries are producing unexpected results when being pushed down to MySql. One example query and resulting error is below. Per Steve H this is a defect for MySql 5.0.15 and later. We need to add compensation logic to deal with non-ASCII range values. SELECT intkey, CHR(CONVERT(bigintegervalue, integer)) FROM BQT1.MediumA WHERE (IntKey > 32) AND (IntKey < 127) ORDER BY intkey Error occurred on connector MySQL_Push<5> - Invalid conversion from type class com.metamatrix.common.types.BlobType with value 'javax.sql.rowset.serial.SerialBlob@1b1395dc' to type class java.lang.Character -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-861) All Teiid Connectors must be modified and packaged as JCA Connectors.

by Ramesh Reddy (JIRA)

All Teiid Connectors must be modified and packaged as JCA Connectors. ---------------------------------------------------------------------- Key: TEIID-861 URL: https://jira.jboss.org/jira/browse/TEIID-861 Project: Teiid Issue Type: Sub-task Affects Versions: 6.3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.3 All the supported connectors in the Teiid project must implement the JCA API according to TEIID-859 and packaged into RAR file format. This also fixes concerns in TEIID-143. Once the Connectors are packaged into RAR file format, when they are deploy in a container, they will hold all the needed dependencies inside the single artifact, which containers know how to deploy and re-load when there is a change. The concern is how this will affect the Designer Integration, and connector type information is exposed to external tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-863) Remove Trusted payload, credential map for authenticating connector sources

by Ramesh Reddy (JIRA)

Remove Trusted payload, credential map for authenticating connector sources --------------------------------------------------------------------------- Key: TEIID-863 URL: https://jira.jboss.org/jira/browse/TEIID-863 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors Affects Versions: 6.3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.3 With TEEID-833 the engine will be deployed to a container and TEIID-199 implements the JAAS based authentication. In the container environment the security credentials are passed contextually to the working thread where they can be accessed. So, the custom home grown solutions like trusted payload and credential mapping are no longer needed. Make sure that "ConnectorContext" exposes the necessary information for the security. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-884) Calling restart on adminapi throws an exception

by Van Halbert (JIRA)

Calling restart on adminapi throws an exception ----------------------------------------------- Key: TEIID-884 URL: https://jira.jboss.org/jira/browse/TEIID-884 Project: Teiid Issue Type: Bug Components: AdminApi, Server Affects Versions: 7.0 Reporter: Van Halbert Assignee: Steven Hawkins Fix For: 7.0 When calling restart on the admin api, the following exception is being thrown: org.teiid.adminapi.AdminComponentException at com.metamatrix.client.ExceptionUtil.convertException(ExceptionUtil.java:65) at com.metamatrix.common.comm.platform.socket.client.SocketServerConnection$ServerConnectionInvocationHandler.invoke(SocketServerConnection.java:235) at $Proxy2.restart(Unknown Source) at org.teiid.test.framework.connection.ConnectionStrategy.configure(ConnectionStrategy.java:129) at org.teiid.test.framework.connection.ConnectionStrategyFactory.createConnectionStrategy(ConnectionStrategyFactory.java:53) at org.teiid.test.framework.TransactionContainer.<init>(TransactionContainer.java:31) at org.teiid.test.framework.transaction.LocalTransaction.<init>(LocalTransaction.java:24) at org.teiid.test.testcases.LocalTransactionTests.getTransactionContainter(LocalTransactionTests.java:32) at org.teiid.test.testcases.LocalTransactionTests.testSingleSourceMultipleCommandsExplicitRollback(LocalTransactionTests.java:56) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: org.teiid.adminapi.AdminComponentException at com.metamatrix.client.ExceptionUtil.convertException(ExceptionUtil.java:65) at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl$RemoteInvocationHandler.invoke(SocketServerInstanceImpl.java:342) at $Proxy2.restart(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.metamatrix.common.comm.platform.socket.client.SocketServerConnection$ServerConnectionInvocationHandler.invoke(SocketServerConnection.java:218) ... 26 more Caused by: com.metamatrix.common.comm.exception.SingleInstanceCommunicationException at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl.exceptionOccurred(SocketServerInstanceImpl.java:205) at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:320) at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl$RemoteInvocationHandler.invoke(SocketServerInstanceImpl.java:334) ... 32 more Caused by: java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:375) at org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.readObjectOverride(ObjectDecoderInputStream.java:57) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:345) at com.metamatrix.common.comm.platform.socket.client.OioOjbectChannelFactory$OioObjectChannel.read(OioOjbectChannelFactory.java:124) at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:314) ... 33 more Its documented that the connection is no longer valid after a restart, and a new one has to be created. However, a restart call should not throw an exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-934) MySql Queries - SQL syntax error on pushdown queries when using functions like LPAD, REPLACE, etc

by Warren Gibson (JIRA)

MySql Queries - SQL syntax error on pushdown queries when using functions like LPAD, REPLACE, etc ------------------------------------------------------------------------------------------------- Key: TEIID-934 URL: https://jira.jboss.org/jira/browse/TEIID-934 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Steven Hawkins Several CTC queries are failing in MySql when they are pushed down to the source. See query example and resulting SQL error below: SELECT INTKEY, LPAD(TIMESTAMPVALUE, 18) FROM BQT1.SmallA ORDER BY INTKEY Error Code:1064 Message:Error Code:1064 Message:Error occurred on connector MySQL_Push<5> - Error Code:1064 Message:You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') AS c_1 FROM smalla AS g_0 ORDER BY c_0' at line 1 Executing statement: [SQL: SELECT cast(g_0.INTKEY AS signed) AS c_0, LPAD(date_format(g_0.TIMESTAMPVALUE, '%Y-%m-%d %H:%i:%S.%f'), 18) AS c_1 FROM smalla AS g_0 ORDER BY c_0] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-893) XML Formatting error in Dynamic VDB (.def) file presents to user as file not found

by Paul Nittel (JIRA)

XML Formatting error in Dynamic VDB (.def) file presents to user as file not found ---------------------------------------------------------------------------------- Key: TEIID-893 URL: https://jira.jboss.org/jira/browse/TEIID-893 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Environment: Fedora 10, Teiid 7.0 M1 snapshot Reporter: Paul Nittel Assignee: Steven Hawkins I created paul.def which contained a connector to Oracle. When I tried to query anything (for example, "SELECT 1;"), I received an error that indicated the paul.def file was not found. After patching Teiid to produce a better message, we found I had fat-fingered the XML in the .def. Would have saved a bunch o' time had the correct error message been shown in the beginning. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-899) Virtual Procedure queries with input variables failing with "No value was available."

by Paul Nittel (JIRA)

Virtual Procedure queries with input variables failing with "No value was available." ------------------------------------------------------------------------------------- Key: TEIID-899 URL: https://jira.jboss.org/jira/browse/TEIID-899 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Environment: Fedora 10; Teiid 7.0.0M1 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: QT_ora11ds.vdb, teiidEXEC.log This does not mean that all virtual procedures with input variables are failing... Just these 3 in particular. Read on! There are 3 queries of virtual procedures that are consistently failing for all sources. For example, this one: EXEC VirtProcs.dyno( '04:00:00', -125 ) gets an exception that reads, "Target exception: com.metamatrix.jdbc.MMSQLException: Error Code:ERR.015.006.0033 Message:Unable to evaluate VIRTPROCS.DYNO.TIMEIN: No value was available". I cranked up the logging to DEBUG and have included the log file (and VDB) in case you want to see more detail. Running this query against these models in a 6.2 Designer, it's OK. I took that VDB, deployed in a 7.0 Teiid, and the query fails. The other failing queries are: SELECT DNT FROM VirtProcs.vDate_n_Time WHERE intkey_in = 2 SELECT intkey , timevalue , bytenum FROM bqt1.largea WHERE largea.intkey IN ( SELECT rs_intkey FROM ( EXEC VirtProcs.dyno ( '04:00:00' , -125 )) AS foo ) The third is really just a variation of the first. Log and VDB are attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-868) Simplify handling of parse format date/time functions

by Steven Hawkins (JIRA)

Simplify handling of parse format date/time functions ----------------------------------------------------- Key: TEIID-868 URL: https://jira.jboss.org/jira/browse/TEIID-868 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 6.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3 There is no need to have separate implementations and pushdown paths for parsedate/parsetime, etc. They should just be rewritten forms of parse/formattimestamp. Also timestampadd is typically implemented to expect and return a timestamp, so non-timestamp forms should be rewritten to the timestamp form. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-912) Add unit test methods from JBEDSP-1137: StackOverflowError when top level query uses the same symbol name and group alias that is in a second level query or sub-query

by Larry O'Leary (JIRA)

Add unit test methods from JBEDSP-1137: StackOverflowError when top level query uses the same symbol name and group alias that is in a second level query or sub-query ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-912 URL: https://jira.jboss.org/jira/browse/TEIID-912 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 7.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Fix For: 7.0 Add test coverage from JBEDSP-1137 that covers the following use case: SELECT CONVERT(A.e2, biginteger) AS e2 FROM ( SELECT CONVERT(e2, long) AS e2 FROM ( SELECT 5 AS e2 ) AS A ) AS A -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2010