February 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1864) TIMESTAMPADD of SQL_TSI_FRAC_SECOND fails for Sybase 15 with JConnect 6.0.5 driver

by Paul Nittel (Created) (JIRA)

TIMESTAMPADD of SQL_TSI_FRAC_SECOND fails for Sybase 15 with JConnect 6.0.5 driver ---------------------------------------------------------------------------------- Key: TEIID-1864 URL: https://issues.jboss.org/browse/TEIID-1864 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Paul Nittel Assignee: Steven Hawkins Executing this query: SELECT intkey, timestampvalue, TIMESTAMPADD(SQL_TSI_FRAC_SECOND,123,TIMESTAMPVALUE) FROM BQT1.SMALLA WHERE INTKEY < 10 ORDER BY INTKEY errors in the following fashion: [JDBCExecutionException] 0: Error Code:0 Message:'JZ0SI: A static function escape timestampaddsql_tsi_frac_second was used which is not supported by this server.' error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.IntKey AS c_0, g_0.TimestampValue AS c_1, {fn timestampadd(SQL_TSI_FRAC_SECOND, 123, g_0.TimestampValue)} AS c_2 FROM SmallA g_0 WHERE g_0.IntKey < 10 ORDER BY c_0] 1 [SQLException]JZ0SI: A static function escape timestampaddsql_tsi_frac_second was used which is not supported by this server. at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:272) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:342) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:118) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:232) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) 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:662) Caused by: java.sql.SQLException: JZ0SI: A static function escape timestampaddsql_tsi_frac_second was used which is not supported by this server. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.processEscapes(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.doEscapeProcessing(Unknown Source) at com.sybase.jdbc3.jdbc.SybPreparedStatement.<init>(Unknown Source) at com.sybase.jdbc3.jdbc.SybConnection.a(Unknown Source) at com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(Unknown Source) at com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(Unknown Source) at com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(Unknown Source) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:465) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:460) at org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:243) at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:172) at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84) ... 13 more Executing the same query using the JTDS 1.2.5 driver works correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
5
0 / 0

[JBoss JIRA] (TEIID-1875) Convert community docs to confluence

by Steven Hawkins (Created) (JIRA)

Convert community docs to confluence ------------------------------------ Key: TEIID-1875 URL: https://issues.jboss.org/browse/TEIID-1875 Project: Teiid Issue Type: Task Components: Documentation Reporter: Steven Hawkins Fix For: 8.0 Our confluence instance https://docs.jboss.org/author/dashboard.action and associated docbook import https://issues.jboss.org/browse/ORG-965 should be used to produce an online version of the docs. Export actions will need to be used in maven the produce distributable forms with our artifacts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1352) Produce Admin API jar containing only Interfaces.

by John Doyle (JIRA)

Produce Admin API jar containing only Interfaces. ------------------------------------------------- Key: TEIID-1352 URL: https://jira.jboss.org/browse/TEIID-1352 Project: Teiid Issue Type: Feature Request Components: AdminApi Reporter: John Doyle Assignee: Steven Hawkins TEIIDDES-175 requires the creation of a target runtime for Teiid so that the tooling can be further abstracted from changes in Teiid. In order to accomplish this the tooling requires an Admin API jar containing only interfaces. The Designer code that depends upon the Admin API could be compiled with this jar, and the plug-in defining the target runtime would load the implementation of the Admin API at runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

7
11
0 / 0

[JBoss JIRA] (TEIID-1820) like_regex only matches full string patterns

by Steven Hawkins (Created) (JIRA)

like_regex only matches full string patterns -------------------------------------------- Key: TEIID-1820 URL: https://issues.jboss.org/browse/TEIID-1820 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.5 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 like_regex currently asks the compiled pattern matcher if the pattern matches in full, not for the first occurrence. This means that a pattern such as 'a' will not match 'cat'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
6
0 / 0

[JBoss JIRA] (TEIID-1834) Add suppot for a comparable binary type

by Steven Hawkins (Created) (JIRA)

Add suppot for a comparable binary type --------------------------------------- Key: TEIID-1834 URL: https://issues.jboss.org/browse/TEIID-1834 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 Teiid currently lacks a binary/varbinary type. Since we have both blob/clob, it would be natural to also introduce a varbinary analog to string. It would be a comparable type and need an escape syntax for entering literals. Translators would need to be modified to account for binary literals. See the forum post for current workarounds. We also as a one off have previously allowed clob types to be comparable, see also TEIID-1248. Another approach would by to allow clob/blob to comparable in Teiid, but possibly not at the source as per the searchability metadata. We would still need to support an escape syntax and modify translators to use native type information and the appropriate literal format. The advantage of this latter approach is that there is nothing more that designer must do to support this case. The most practical benefit from introducing a varbinary type would be in having a better size estimate (it would be limited to 8000 bytes) for buffering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
6
0 / 0

[JBoss JIRA] (TEIID-1901) Redo Quick Start guide for Teiid 8.0 changes

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1901: ----------------------------------- Summary: Redo Quick Start guide for Teiid 8.0 changes Key: TEIID-1901 URL: https://issues.jboss.org/browse/TEIID-1901 Project: Teiid Issue Type: Task Components: Documentation Reporter: Ramesh Reddy Fix For: 8.0 Currently the Quick start document for 8.0 still shows the techniques used with the Teiid 7 as per data creation deployment etc. This needs be revised for 8.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
2
0 / 0

[JBoss JIRA] (TEIID-1879) Teradata Query Testing - Unhandled exception causing SOCKET CLOSED condition

by Warren Gibson (Created) (JIRA)

Teradata Query Testing - Unhandled exception causing SOCKET CLOSED condition ---------------------------------------------------------------------------- Key: TEIID-1879 URL: https://issues.jboss.org/browse/TEIID-1879 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Warren Gibson Assignee: Steven Hawkins Attachments: Teradata_log_vqt Testing Teradata as a source with Teiid 7.6 produces a SOCKET CLOSED condition on the below query and all VQT queries following it. SELECT * FROM VQT.Mapping1 ORDER BY IntKey There is an unhandled exception in the attached log. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
3
0 / 0

[JBoss JIRA] (TEIID-1867) Duplicate metadata for multisource models

by Andriy Rokhmanov (Created) (JIRA)

Duplicate metadata for multisource models ----------------------------------------- Key: TEIID-1867 URL: https://issues.jboss.org/browse/TEIID-1867 Project: Teiid Issue Type: Bug Affects Versions: 7.5 Environment: Windows 7, JBoss 5.1.0, java version 1.6.0_22 - 64 bit. Reporter: Andriy Rokhmanov Assignee: Steven Hawkins Attachments: chorus-vdb.xml When more than one multi-source model defined in single VDB, the tables from one multi-source schema appear in the another one. See screenshot and sample vdb attached. The issue reproducible on our side with file, h2 and hsqldb multi-source models. We have to define only one multi-source model per vdb to avoid the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
9
0 / 0

[JBoss JIRA] (TEIID-1922) BaseDelegateTranslator's start method is being called before the delegate execution factory is set.

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1922: ----------------------------------- Summary: BaseDelegateTranslator's start method is being called before the delegate execution factory is set. Key: TEIID-1922 URL: https://issues.jboss.org/browse/TEIID-1922 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 7.4 Reporter: Ramesh Reddy Assignee: Steven Hawkins Priority: Minor Fix For: 7.7 BaseDelegatingTranslator's start method is called before the setDeletegate is called to set the delegate name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
2
0 / 0

[JBoss JIRA] (TEIID-1872) Implicit temp table creation fails with insert and explicit columns

by Steven Hawkins (Created) (JIRA)

Implicit temp table creation fails with insert and explicit columns ------------------------------------------------------------------- Key: TEIID-1872 URL: https://issues.jboss.org/browse/TEIID-1872 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 7.6 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6.1, 8.0 using something like: insert into #x (y,z) select ... will fail since we are defining #x using the query expression. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2012