June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1077) Split all Connector projects to define their "Translator" modules and "Connection" modules

by Ramesh Reddy (JIRA)

Split all Connector projects to define their "Translator" modules and "Connection" modules ------------------------------------------------------------------------------------------ Key: TEIID-1077 URL: https://jira.jboss.org/jira/browse/TEIID-1077 Project: Teiid Issue Type: Sub-task Components: Connector API, JDBC Connector, LDAP Connector, Misc. Connectors, Salesforce Connector, XML Connector Reporter: Ramesh Reddy Split all the connector projects as follows connector-jdbc --> translator-jdbc connector-ldap --> translator-ldap/connector-ldap connector-loopback -> translator-loopback connector-salesforce -> translator-sf/connector-sf (more investigation on this) connector-text -> translator-text/connector-text connector-xml (file, http, soap) --> TBD ( these will not be jca connectors, alternative methods needs to be investigated) -- 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, 8 months

3
6
0 / 0

[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, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1015) Move threading concerns to the engine

by Steven Hawkins (JIRA)

Move threading concerns to the engine ------------------------------------- Key: TEIID-1015 URL: https://jira.jboss.org/jira/browse/TEIID-1015 Project: Teiid Issue Type: Quality Risk Components: Connector API, Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 With the JCA changes we need to more threading concerns primarily to the engine. This move is motivated by transactional connector work needing to execute serially - where the transaction lock is held by the calling thread (a request workitem thread from DQPCore). We should also forgo the creation of random xids for request and local scoped transactions, rather we can just use the TransactionManager directly like with Teiid 6.2. -- 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, 8 months

2
2
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, 8 months

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, 8 months

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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1036) AdminShell & Migrate shell scripts should be executable

by Paul Nittel (JIRA)

AdminShell & Migrate shell scripts should be executable ------------------------------------------------------- Key: TEIID-1036 URL: https://jira.jboss.org/jira/browse/TEIID-1036 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 7.0 Environment: Fedora 12, Iced Tea 1.6 Reporter: Paul Nittel Assignee: Steven Hawkins Both of these scripts unzip without executable permissions. Other JBoss shell scripts are executable "out of the box" and Teiid's should be as well. Please package these--and any other shell scripts we may create--as executable. -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1020) Remove the use of Teiid specific JDBC extensions

by Steven Hawkins (JIRA)

Remove the use of Teiid specific JDBC extensions ------------------------------------------------ Key: TEIID-1020 URL: https://jira.jboss.org/jira/browse/TEIID-1020 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 The JDBC extensions need to have their functionality provided by alternative means to still work in other scenarios (such as odbc). At a minimum we should remove: DatabaseMetaData - schemas should be available via a system procedure getXMLSchemas that returns the results as SQLXMLs. This also fixes potential memory issues with retrieving lots of schemas. Connection - vdbversion will probably go away and is available via the system tables ResultSet - processing times are now local to the client, if they want to track timings then they can use a spy driver, stopwatch code, etc. ResultSetMetaData - the vdb name is already accessible through the system tables and through the standard connection method getCatalog. the number of parameters should be coming from parametermetadata (not yet implemented) Statement will take some more thought. We may want to move the xslt processing off to a system function similar to http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.... The other functionality will be hard to move as well. -- 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, 8 months

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, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-1044) Export connection factory does not always correct properties

by Ramesh Reddy (JIRA)

Export connection factory does not always correct properties ------------------------------------------------------------ Key: TEIID-1044 URL: https://jira.jboss.org/jira/browse/TEIID-1044 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 In 7.0 M3, the admin method "exportConnectionFactory" method is based on the "ManagedDeployment" object. i.e. instead exposing the CF, this method gets to the file that originally defined this CF and simply exposes it. If there are any modifications thru JOPR tool those modifications will not be picked up by this export. Also, if user originally defined more than one CF inside the same "-ds.xml" file, then the export will get contents of the file as is, thus exposing more than it needs to. -- 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, 8 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010