October 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-867) Possibly Teiid embedded clients (Designer) not pinging query engine, causing session timeouts

by Paul Nittel (JIRA)

Possibly Teiid embedded clients (Designer) not pinging query engine, causing session timeouts --------------------------------------------------------------------------------------------- Key: TEIID-867 URL: https://jira.jboss.org/jira/browse/TEIID-867 Project: Teiid Issue Type: Bug Environment: fedora 10, Teiid Designer 6.2 Reporter: Paul Nittel Assignee: Steven Hawkins I started the Teiid 6.2 Designer, executed a VDB and ran a simple query. Then I waited about 35 minutes and finally clicked the Running Dude(tm) button. Instead of nicely arranged rows of data, I got: Error 2009-09-30 14:41:48.107 Error processing query com.metamatrix.jdbc.MMSQLException: Error trying to execute a statement select IntKey, StringKey, IntNum, StringNum, FloatNum, LongNum, DoubleNum, ByteNum, DateValue, TimeValue, TimestampValue, BooleanValue, CharValue, ShortValue, BigIntegerValue, BigDecimalValue, ObjectValue from "SP"."BQT2.SmallA" . at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:116) at com.metamatrix.jdbc.MMStatement.executeSql(MMStatement.java:414) at com.metamatrix.jdbc.MMStatement.execute(MMStatement.java:318) at net.sourceforge.sqlexplorer.sqlpanel.SqlExecProgress.processQuery(SqlExecProgress.java:192) at net.sourceforge.sqlexplorer.sqlpanel.SqlExecProgress.run(SqlExecProgress.java:121) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: com.metamatrix.jdbc.MMSQLException: The specified session ID "2" is invalid. It cannot be found in the userbase. at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:123) at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:71) at com.metamatrix.jdbc.MMStatement.sendRequestMessageAndWait(MMStatement.java:855) at com.metamatrix.jdbc.MMStatement.executeSql(MMStatement.java:410) ... 4 more Caused by: [MetaMatrixComponentException]The specified session ID "2" is invalid. It cannot be found in the userbase. 1 [InvalidSessionException]The specified session ID "2" is invalid. It cannot be found in the userbase. at com.metamatrix.client.ExceptionUtil.convertException(ExceptionUtil.java:59) at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:119) at $Proxy24.executeRequest(Unknown Source) at com.metamatrix.jdbc.MMStatement.sendRequestMessageAndWait(MMStatement.java:853) ... 5 more Caused by: [InvalidSessionException]The specified session ID "2" is invalid. It cannot be found in the userbase. at com.metamatrix.platform.security.session.service.SessionServiceImpl.getSessionInfo(SessionServiceImpl.java:295) at com.metamatrix.platform.security.session.service.SessionServiceImpl.validateSession(SessionServiceImpl.java:287) at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:109) ... 7 more The session timeout property is commented out in the workspace.properties file. Steve Hawkins opined the embedded clients ae not pinging the server. -- 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

15 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-750) Add more filtering in the internal processing of queries so that hidden items do not requires fully qualified names to be used

by Rob Hutton (JIRA)

Add more filtering in the internal processing of queries so that hidden items do not requires fully qualified names to be used ------------------------------------------------------------------------------------------------------------------------------ Key: TEIID-750 URL: https://jira.jboss.org/jira/browse/TEIID-750 Project: Teiid Issue Type: Feature Request Components: Query Engine, Server Affects Versions: 6.1.0 Reporter: Rob Hutton Assignee: Steven Hawkins If you have a table in a source model and a table in a view model with the same name, you must use the fully qualified name of the view model table when querying the VDB even if the source model is not visible. It would be nice if the visibility flag was taken in to account when trying to resolve object names while querying the VDB -- 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

15 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-865) WS-Relational SOAP Connector is sending empty SOAP-ACTION header.

by John Doyle (JIRA)

WS-Relational SOAP Connector is sending empty SOAP-ACTION header. ----------------------------------------------------------------- Key: TEIID-865 URL: https://jira.jboss.org/jira/browse/TEIID-865 Project: Teiid Issue Type: Bug Components: XML Connector Affects Versions: 6.2.0, 6.1.0 Reporter: John Doyle Assignee: John Doyle Fix For: 6.3 The XML-Relational SOAP connector is not picking up the SOAP-Action from the model and placing it in the correct HTTP Header. -- 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

15 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-808) Revisit the prior issues with extending the JOPR JMX plugin and verify if the problems have been fixed

by Van Halbert (JIRA)

Revisit the prior issues with extending the JOPR JMX plugin and verify if the problems have been fixed ------------------------------------------------------------------------------------------------------ Key: TEIID-808 URL: https://jira.jboss.org/jira/browse/TEIID-808 Project: Teiid Issue Type: Sub-task Components: Jopr Plugin Reporter: Van Halbert Assignee: Ted Jones In the development of the tech preview of MetaMatrix 5.5.3 version, it was determined that the JOPR JMX plugin had issues that did not enable us to extend for our use. This needs to be revisited because this is our first choice for discovering datasources (since JOPR is already doing it). We need to perform a filtering process which requires us to be able to discover and then interrogate the properties in order to determine if this is a Teiid datasource. -- 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

15 years, 6 months

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-754) LOCATE() function isn't being translated correctly by Oracle Connector

by Larry O'Leary (JIRA)

LOCATE() function isn't being translated correctly by Oracle Connector ---------------------------------------------------------------------- Key: TEIID-754 URL: https://jira.jboss.org/jira/browse/TEIID-754 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0, 6.0.0, 6.2.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Fix For: 6.2.0 The rewritten/translated query for the MMx LOCATE() function to Oracle's instr() function does not appear to be correct. SELECT locate(INTNUM, '234567890', 1) FROM SMALLA WHERE INTKEY = 26 Is being rewritten for Oracle as: SELECT instr('234567890', to_char(SmallA.IntNum), 2) FROM SmallA WHERE SmallA.IntKey = 26 In this case Oracle will return 0 for instr() because Oracle starts at position 1. The query should be: SELECT instr('234567890', to_char(SmallA.IntNum), 1) FROM SmallA WHERE SmallA.IntKey = 26 Furthermore, if I pass a negative value to LOCATE() it appears we assume position 1. If the negative value is sent to Oracle, Oracle goes from the end of the string. We should prevent this (if not already). In 5.5.1 the rewritten query is even different and may ore may not be correct. I have not checked 5.5.3/5.5.4 and/or Westport/Teiid. Here are the test cases that should cover this issue: public void testRewriteLocate() throws Exception { String input = "SELECT locate(INTNUM, 'chimp', 1) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', to_char(SmallA.IntNum), 1) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate2() throws Exception { String input = "SELECT locate(STRINGNUM, 'chimp') FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', SmallA.StringNum) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate3() throws Exception { String input = "SELECT locate(INTNUM, '234567890', 1) FROM SMALLA WHERE INTKEY = 26"; //$NON-NLS-1$ String output = "SELECT instr('234567890', to_char(SmallA.IntNum), 1) FROM SmallA WHERE SmallA.IntKey = 26"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate4() throws Exception { String input = "SELECT locate('c', 'chimp', 1) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT 1 FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate5() throws Exception { String input = "SELECT locate(STRINGNUM, 'chimp', -5) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', SmallA.StringNum, 1) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } -- 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

15 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-807) Develop the new Teiid Console using JOPR for its core framework

by Van Halbert (JIRA)

Develop the new Teiid Console using JOPR for its core framework --------------------------------------------------------------- Key: TEIID-807 URL: https://jira.jboss.org/jira/browse/TEIID-807 Project: Teiid Issue Type: Feature Request Components: Console, Jopr Plugin Affects Versions: 6.3.0 Reporter: Van Halbert Assignee: Van Halbert Use the the JOPR framework to develop the new Teiid console for administrating and monitoring a Teiid resource. -- 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

15 years, 6 months

4
6
0 / 0

[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

15 years, 6 months

2
4
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

15 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

15 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

15 years, 6 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2009