December 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-739) JDBC Connector updates

by Steven Hawkins (JIRA)

JDBC Connector updates ---------------------- Key: TEIID-739 URL: https://jira.jboss.org/jira/browse/TEIID-739 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 The PostgreSQL translator should assume the use of a 8.0 jdbc client (supports back to the 7.2 server) so that we can remove DatePartFunctionModifer/ModifiedDatePartFunctionModifer also support for the bit functions should be added. The SQL Server translator / capabilities should be updated to assume the use of a 2005, DataDirect, or later driver (all support back to sql server 2000) so that support for most of the time functions can be added. -- 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-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-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-847) Constant conversion issue

by Steven Hawkins (JIRA)

Constant conversion issue ------------------------- Key: TEIID-847 URL: https://jira.jboss.org/jira/browse/TEIID-847 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 criteria such as convert(BQT1.SmallA.LongNum, bigdecimal) = '22.0' is being treated as false criteria since the resolverutil checks for a narrowing conversion using the equality method (which will not work for bigdecimals in JRE 1.6). -- 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-858) DependentSetCriteria not being replaced

by Steven Hawkins (JIRA)

DependentSetCriteria not being replaced --------------------------------------- Key: TEIID-858 URL: https://jira.jboss.org/jira/browse/TEIID-858 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3 This is a regression from TEIID-308. If the DependentAccessNode is not performing the expansion, then the criteria is not replaced. -- 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-897) Create a new autowrap mode to replace pessimistic/optimistic

by Steven Hawkins (JIRA)

Create a new autowrap mode to replace pessimistic/optimistic ------------------------------------------------------------ Key: TEIID-897 URL: https://jira.jboss.org/jira/browse/TEIID-897 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 There are issues with pessimistic/optimistic autowrap modes: 1. optimistic transaction autowrap is no longer needed since all installations of Teiid have a transaction manager available. This mode is really only useful as a development time aid - there is also a case to replace it with a readonly mode to prevent all updates. 2. the detection of when a transaction is needed is based upon the resolved from of a command and not the actual plan/execution. This has led to progressively more pessimistic logic to capture when a transaction is needed (being fully pessimistic we'd have to assume that any procedure with an update count of 1 also needs a transaction since an error can occur during the conversion of output parameters that should cause a rollback). We should either do a better job based upon the plan/execution, or just state simple assumptions (select -no txn, source insert, update, delete, exec w/ update count <=1 -no txn, else txn). 3. the terminology is confusing since it's evocative of locking semantics I therefore propose we change these to txnAutoWrap=AUTO, which would be similar to pessimistic mode and would change the detection strategy to one of the proposals from 2. We should also be explicit that this mode is based upon the assumption that multiple selects do not need to be grouped in the same transaction. However when there is a transaction, then the selects will be performed in the same transaction. -- 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-430) Root access needs enforced for subsystem admin api edits of security properties

by Steven Hawkins (JIRA)

Root access needs enforced for subsystem admin api edits of security properties ------------------------------------------------------------------------------- Key: TEIID-430 URL: https://jira.jboss.org/jira/browse/TEIID-430 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 Using the subsystem admin api (not exposed directly by any client) you can modify the security configuration properties as a product admin instead of root (this is only enforced by the console). We should enforce this on the server side 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, 6 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2009