December 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-806) JDBC connector handling of convert is inconsistent

by Steven Hawkins (JIRA)

JDBC connector handling of convert is inconsistent -------------------------------------------------- Key: TEIID-806 URL: https://jira.jboss.org/jira/browse/TEIID-806 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3.0 If a source lacks the exact representation of a Teiid type we approximate it with the closest source type. Pushed converts will typically not have the same affect as if they are evaluated in the engine. For example sources lacking byte or tinyint types are having conversions dropped rather, but the actual effect should be modulo the max byte value. We also are not ensuring that the truncation or rounding behavior is the same for all conversions - such as from a floating point number to a fixed point. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-851) API improvements for custom connector development

by Mark Drilling (JIRA)

API improvements for custom connector development ------------------------------------------------- Key: TEIID-851 URL: https://jira.jboss.org/jira/browse/TEIID-851 Project: Teiid Issue Type: Feature Request Components: Connector API Affects Versions: 6.1.0 Reporter: Mark Drilling Assignee: Steven Hawkins Priority: Minor I'm building a custom connector, and I was trying to figure out a way to get information on whether or not a certain column in a Source Model is a Primary or Foreign Key. Here's an example of the code I've been trying: MetadataID mdID = group.getMetadataID(); //group is an IGroup String tableName = metadata.getObject(mdID).getNameInSource(); However, there doesn't appear to be a way to determine which column is Primary or Foreign Key. One thing I did notice playing around with the API, the MetadataObject contains a TableRecordImpl object that contains all sorts of MetaData info. That class appears to have tons of great info, along with getters and setters, including one called getForeignKeyIDs. Don't know if there's maybe a reason it's abstracted such that we can't get to it, but being able to get that and the other info out of that object could be highly beneficial. Maybe this is something that could be added to the API in the future? -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-864) Need new deployment packing that works with JBoss AS or JBoss Embedded

by Ramesh Reddy (JIRA)

Need new deployment packing that works with JBoss AS or JBoss Embedded ---------------------------------------------------------------------- Key: TEIID-864 URL: https://jira.jboss.org/jira/browse/TEIID-864 Project: Teiid Issue Type: Sub-task Components: Build/Kits Affects Versions: 6.3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.3 Once all Connectors are in RAR format, and engine in RAR format the old deployment needs to be removed and new deployment needs to be defined, where a user can use in combination with JBoss based containers. Basically, this process needs to combine all the resources in similar directory structure with JBoss Tools, where a user can download JBoss AS or JBoss Embeeded and overlay the Teiid deployment on top of it and start using it. To begin with Teiid will only support JBoss Container, however it should be easy enough to support any JCA container, as all the components are written to JCA API. If community is interested they can use either Jenks or Glassfish containers, however the configuration needs to be developed for those containers. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-859) Connector API must extend the JCA 1.5 API

by Ramesh Reddy (JIRA)

Connector API must extend the JCA 1.5 API ----------------------------------------- Key: TEIID-859 URL: https://jira.jboss.org/jira/browse/TEIID-859 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors Affects Versions: 6.3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.3 The connector API must be modified such that it extends the JCA API http://java.sun.com/j2ee/connector/ This will enable Teiid Connectors be used as JEE Connectors in a JEE container. By the end it will pass as "JCA" connector with Teiid specific extensions (Current API). The Connector API base classes should provide skeleton adaptors for the JCA API. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-883) Convert model/group/element to schema/table/column

by Steven Hawkins (JIRA)

Convert model/group/element to schema/table/column -------------------------------------------------- Key: TEIID-883 URL: https://jira.jboss.org/jira/browse/TEIID-883 Project: Teiid Issue Type: Sub-task Components: Documentation Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 The non-standard terms model/group/element should be changed to schema/table/column. This affects our runtime metadata object names, system tables, documentation, and error messages. The model to schema change represents a bit of a mismatch between the designer view of the world and Teiid. Designer models are allowed to contain catalog and schemas, but at runtime they simply become part of the table name. -- 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, 7 months

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

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

4
3
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, 7 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2009