April 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1009) BQT Pushdown query "ORDER BY" is not always ordering results properly

by Warren Gibson (JIRA)

BQT Pushdown query "ORDER BY" is not always ordering results properly --------------------------------------------------------------------- Key: TEIID-1009 URL: https://jira.jboss.org/jira/browse/TEIID-1009 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Steven Hawkins Pushdown queries with "ORDER BY" are not always returning results in correct order. The below query is returning query results in the wrong order for Pushdown on DB2, MySql, Ora9-10-11, and SqlServer sources. If BQT1.SmallA.StringKey is placed in the SELECT clause the results are returned in the correct order. SELECT BQT1.SmallA.IntNum, BQT2.SmallB.StringNum FROM BQT1.SmallA, BQT2.SmallB WHERE BQT1.SmallA.IntNum = BQT2.SmallB.StringNum AND BQT1.SmallA.IntKey >= 5 AND BQT2.SmallB.IntKey >= 5 ORDER BY BQT1.SmallA.StringKey -- 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

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-1081) Provide pre built "Translator" for all the popular data sources

by Ramesh Reddy (JIRA)

Provide pre built "Translator" for all the popular data sources --------------------------------------------------------------- Key: TEIID-1081 URL: https://jira.jboss.org/jira/browse/TEIID-1081 Project: Teiid Issue Type: Sub-task Components: Build/Kits, JDBC Connector, LDAP Connector, Misc. Connectors Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Out of the box provide the pre-built "translators" for all the sources Teiid supports like - Oracle, SQLServer, MySQL etc. - Text - Loopback - LDAP - Sales Force - XML ?? -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIID-900) Refine option no cache behavior

by Steven Hawkins (JIRA)

Refine option no cache behavior ------------------------------- Key: TEIID-900 URL: https://jira.jboss.org/jira/browse/TEIID-900 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 Currently specifying option no cache with a particular group name cascades fully through all materialized views. It would be better if it only applied to a single level. Simply specifying option no cache without any specific groups would continue to behave the same way as it does currently, which bypasses cache for all materialized views. The materialized view scripts should be changed to SELECT ... INTO ... FROM x OPTION NOCACHE x so that the loads can take advantage of intermediate materialized view layers. -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIID-871) Refactor system vdb

by Steven Hawkins (JIRA)

Refactor system vdb ------------------- Key: TEIID-871 URL: https://jira.jboss.org/jira/browse/TEIID-871 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 6.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3 1. We should remove the system physical model - it's undocumented, exposes too much metadata cruft, and requires too much logic in the index connector to support it. 2. We should remove System.datatypeelements and System.datatypeelementproperties - the transformations are invalid (they will always return no rows) and they are redundant 3. There should be a new system table ProcedureParamProperties that exposes annotations for procedure params. with System.element/datatype and the corresponding properties tables. 4. This one is open to debate, but I would also like to remove System.describe - since annotations are available directly on the appropriate type table, there doesn't seem to be a good reason to introduce a procedure that operates over all metadata records to return the same information. -- 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-749) Replace the TestNoArgConnector Test with an integration test.

by John Doyle (JIRA)

Replace the TestNoArgConnector Test with an integration test. ------------------------------------------------------------- Key: TEIID-749 URL: https://jira.jboss.org/jira/browse/TEIID-749 Project: Teiid Issue Type: Task Components: XML Connector Affects Versions: 6.2.0 Reporter: John Doyle Assignee: John Doyle Priority: Minor Fix For: 6.2.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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1075) Separate Connector Binding into Translation Layer and Connection Layer

by Ramesh Reddy (JIRA)

Separate Connector Binding into Translation Layer and Connection Layer ---------------------------------------------------------------------- Key: TEIID-1075 URL: https://jira.jboss.org/jira/browse/TEIID-1075 Project: Teiid Issue Type: Feature Request Components: Connector API, Query Engine Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Priority: Blocker Fix For: 7.0 Connector Binding = Translation Layer + Connection this association needs to be broken down into individual concerns as Translation Layer is concern of the Teiid and Connection semantics are more general purpose. By making this change Teiid configuration can be stable across deployment environments. Also, the translation layer then can be free of JCA semantics. The Connection layer then can be JCA Connection or provided by any Connection provider. -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIID-1012) Update logging contexts

by Steven Hawkins (JIRA)

Update logging contexts ----------------------- Key: TEIID-1012 URL: https://jira.jboss.org/jira/browse/TEIID-1012 Project: Teiid Issue Type: Quality Risk Components: Common Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 We should consolidate logging contexts to make documenting their use easier. -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIID-741) SQL Server type hadling issues

by Steven Hawkins (JIRA)

SQL Server type hadling issues ------------------------------ Key: TEIID-741 URL: https://jira.jboss.org/jira/browse/TEIID-741 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 If we pushdown a convert(stringvalue, char) function, it turns into the source expression convert(char, stringvalue), which has the following problems: it defaults to type char(30) which is right padded, it is not trimmed since the target type was Char and the trim logic looks only for String. Also it does not account for empty string mapping to null. The SQL Server tinyint type is unsigned. Our import needs to be modified to this to short, since our byte type is unsigned. Pushing down a convert(numericvalue, byte) as convert(tinyint, numericvalue) is problematic if the byte values are stored in a signed manner. -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIID-876) Server Times Out Session Despite Configuration

by Nestor D. Rodriguez (JIRA)

Server Times Out Session Despite Configuration ---------------------------------------------- Key: TEIID-876 URL: https://jira.jboss.org/jira/browse/TEIID-876 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.2.0 Environment: Solaris 10 Reporter: Nestor D. Rodriguez Assignee: Steven Hawkins I have a Teiid server set up on a Solaris 10 machine. The deploy.properties file has the session.expirationTimeInMilli property commented out to avoid any sessions timing out. Nevertheless, when connecting to the server using the adminshell tool, I inevitable get the following error in the tool after five or so minutes: Exception in thread "SocketPing" java.net.SocketException: Socket closedjava.net.SocketException: Socket closedjava.net.SocketException: Socket closedSocket closed at com.metamatrix.client.ExceptionUtil.convertException(ExceptionUtil.java: 75) at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl$RemoteInvocationHandler.invoke(SocketServerInstanceImpl.java:342) at $Proxy0.logoff(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) at $Proxy0.logoff(Unknown Source) at com.metamatrix.common.comm.platform.socket.client.SocketServerConnection.shutdown(SocketServerConnection.java:258) at com.metamatrix.common.comm.platform.socket.client.SocketServerConnection.shutdown(SocketServerConnection.java:248) at com.metamatrix.common.comm.platform.socket.client.SocketServerConnection$1.run(SocketServerConnection.java:113) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: com.metamatrix.common.comm.exception.SingleInstanceCommunicationException: java.net.SocketException: Socket closed at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl.send(SocketServerInstanceImpl.java:179) at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl$RemoteInvocationHandler.invoke(SocketServerInstanceImpl.java:330) ... 12 more Caused by: java.util.concurrent.ExecutionException: java.net.SocketException: Socket closed at com.metamatrix.dqp.client.ResultsFuture.convertResult(ResultsFuture.java:94) at com.metamatrix.dqp.client.ResultsFuture.get(ResultsFuture.java:89) at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl.send(SocketServerInstanceImpl.java:176) ... 13 more Caused by: java.net.SocketException: Socket closed at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at java.io.DataOutputStream.flush(DataOutputStream.java:106) at org.teiid.netty.handler.codec.serialization.ObjectEncoderOutputStream.flush(ObjectEncoderOutputStream.java:71) at com.metamatrix.common.comm.platform.socket.client.OioOjbectChannelFactory$OioObjectChannel.write(OioOjbectChannelFactory.java:142) at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl.send(SocketServerInstanceImpl.java:175) ... 13 more Once this happens, the connection is closed and any attempt to re-connect gives me the message "Failed to connect: (Timer already connected.)" I don't know if it's relevant, but I've also noted that when I run my test JDBC query program, I get my results back, but this message shows up in the teiid.log file: java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcher.read0(Natve Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233) at sun.nio.ch.IOUtil.read(IOUtil.java:206) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236) at org.jboss.netty.buffer.HeapChannelBuffer.setBytes(HeapChannelBuffer.java:163) at org.jboss.netty.buffer.AbstractChannelBuffer.writeBytes(AbstractChannelBuffer.java:429) at org.jboss.netty.channel.socket.nio.NioWorker.readIntoHeapBuffer(NioWorker.java:282) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:254) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:163) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- 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

4
5
0 / 0

[JBoss JIRA] Created: (TEIID-1032) Change nomenclature of "Connector Binding" to "Connection Factory"

by Ramesh Reddy (JIRA)

Change nomenclature of "Connector Binding" to "Connection Factory" ------------------------------------------------------------------ Key: TEIID-1032 URL: https://jira.jboss.org/jira/browse/TEIID-1032 Project: Teiid Issue Type: Sub-task Components: Build/Kits, Common, Connector API, Documentation Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 With the migration of Connectors to the JCA container, using the name "Connector Binding" is different than that of "Connection Factory" usage in the container world. Change all the references in code, pubic api and documentation to reflect the name change -- 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
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2010