January 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4653) SybaseIQ translator: Input parameter not set in prepared statement in source command

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4653?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4653: ---------------------------------- Fix Version/s: 9.2.1 (was: 9.2) > SybaseIQ translator: Input parameter not set in prepared statement in source command > ------------------------------------------------------------------------------------ > > Key: TEIID-4653 > URL: https://issues.jboss.org/browse/TEIID-4653 > Project: Teiid > Issue Type: Sub-task > Components: JDBC Connector > Affects Versions: 8.12.8.6_3 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.2.1 > > > There seems to be problem with prepared statements which are being push to the datasource without binding parameters. > The query engine fails with following error: > {code} > 13:08:00,044 WARN [org.teiid.CONNECTOR] (Worker18_QueryProcessorQueue72) Connector worker process failed for atomic-request=PYp5BTTPF3pK.25.0.16: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [{ts '2000-01-01 00:00:03.0'}] SQL: SELECT g_0."intkey", g_0."timestampvalue" FROM "bqt-server"."dvqe"."SmallA" AS g_0 WHERE g_0."timestampvalue" = ?] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:366) > at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source) [:1.7.0_71] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_71] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_71] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy80.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71] > Caused by: java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 0. > at com.sybase.jdbc4.jdbc.ErrorMessage.raiseError(Unknown Source) > at com.sybase.jdbc4.tds.TdsParam.prepareForSend(Unknown Source) > at com.sybase.jdbc4.jdbc.ParamManager.checkParams(Unknown Source) > at com.sybase.jdbc4.tds.TdsCursor.a(Unknown Source) > at com.sybase.jdbc4.tds.TdsCursor.open(Unknown Source) > at com.sybase.jdbc4.jdbc.SybStatement.executeQuery(Unknown Source) > at com.sybase.jdbc4.jdbc.SybPreparedStatement.executeQuery(Unknown Source) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1] > ... 17 more > {code} > The message indicates, that a prepared statement which is being pushed has not bound parameter values set. > h2.First Example > Example query: > {code:sql} > SELECT IntKey, timestampvalue FROM BQT1.SmallA WHERE timestampvalue = TIMESTAMPCREATE( {d'2000-01-01'}, {t'00:00:03'}) > {code} > Resulting DATA SRC COMMAND: > {code:sql} > SELECT g_0.intkey, g_0.timestampvalue FROM BQT1.SmallA AS g_0 WHERE g_0.timestampvalue = {ts'2000-01-01 00:00:03.0'} > {code} > Resulting SOURCE SRC COMMAND: > {code:sql} > [SELECT g_0."intkey", g_0."timestampvalue" FROM "bqt-server"."dvqe"."SmallA" AS g_0 WHERE g_0."timestampvalue" = ?] > {code} > h2. Second example > Query: > {code:sql} > SELECT bqt2.smalla.intkey, g2.intkey, bqt2.smalla.bytenum FROM bqt2.smalla LEFT JOIN LATERAL (SELECT intkey FROM bqt2.mediuma WHERE bqt2.smalla.bytenum = bqt2.mediuma.bytenum) AS g2 ON true ORDER BY bqt2.smalla.intkey, g2.intkey > {code} > DATA SRC COMMAND 1: > {code:sql} > SELECT g_0.bytenum, g_0.intkey FROM BQT2.SmallA AS g_0 > {code} > SOURCE SRC COMMAND 1: > {code:sql} > [SELECT g_0."bytenum", g_0."intkey" FROM "bqt-server"."dvqe"."SmallA" AS g_0] > {code} > DATA SRC COMMAND 2: > {code:sql} > SELECT g_0.intkey FROM BQT2.MediumA AS g_0 WHERE g_0.bytenum = -128 > {code} > SOURCE SRC COMMAND 2: > {code:sql} > [SELECT g_0."intkey" FROM "bqt-server"."dvqe"."MediumA" AS g_0 WHERE g_0."bytenum" = ?] > {code} > h4.Note: > There should be more DATA SRC commands similar to DATA SRC COMMAND 2, as such query should be performed in a loop for every result from DATA SRC COMMAND 1. But due to error in DATA SRC COMMAND 2, the loop is ended. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4669) Issues with jConnect and Sybase IQ

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4669?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4669: ---------------------------------- Fix Version/s: 9.2.1 (was: 9.2) > Issues with jConnect and Sybase IQ > ---------------------------------- > > Key: TEIID-4669 > URL: https://issues.jboss.org/browse/TEIID-4669 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2.1 > > > jConnect is not as fully-featured as the SQL Anywhere driver, to support it we may need to drop some pushdown and other support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4652) SybaseIQ translator: DAYOFYEAR function not pushed correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4652?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4652: ---------------------------------- Fix Version/s: 9.2.1 (was: 9.2) > SybaseIQ translator: DAYOFYEAR function not pushed correctly > ------------------------------------------------------------ > > Key: TEIID-4652 > URL: https://issues.jboss.org/browse/TEIID-4652 > Project: Teiid > Issue Type: Sub-task > Components: JDBC Connector > Affects Versions: 8.12.8.6_3 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 9.2.1 > > > DAYOFYEAR function is being pushed into SAP IQ datasource causing an error. The function doesn't seem to be supported directly in SAP IQ according to [SAP IQ docs|http://help.sap.com/saphelp_iq1611_iqrefbb/helpdata/en/a5/2b07be84f2...] > Query used: > {code:sql} > SELECT IntKey, datevalue, DAYOFYEAR(datevalue) AS DayFromDate FROM BQT1.SmallA ORDER BY IntKey > {code} > Source query pushed: > {code:sql} > [SELECT g_0."intkey" AS c_0, g_0."datevalue" AS c_1, {fn dayofyear(g_0."datevalue")} AS c_2 FROM "bqt-server"."dvqe"."SmallA" AS g_0 ORDER BY c_0] > {code} > Causing an error coming from SAP IQ: > {code} > 09:08:30,130 WARN [org.teiid.CONNECTOR] (Worker11_QueryProcessorQueue58) Connector worker process failed for atomic-request=PYp5BTTPF3pK.20.0.12: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."intkey" AS c_0, g_0."datevalue" AS c_1, {fn dayofyear(g_0."datevalue")} AS c_2 FROM "bqt-server"."dvqe"."SmallA" AS g_0 ORDER BY c_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:366) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_71] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_71] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_71] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_71] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy80.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71] > Caused by: java.sql.SQLException: JZ0SI: A static function escape dayofyear was used which is not supported by this server. > at com.sybase.jdbc4.jdbc.ErrorMessage.raiseError(Unknown Source) > at com.sybase.jdbc4.jdbc.SybStatement.processEscapes(Unknown Source) > at com.sybase.jdbc4.jdbc.SybStatement.doEscapeProcessing(Unknown Source) > at com.sybase.jdbc4.jdbc.SybPreparedStatement.<init>(Unknown Source) > at com.sybase.jdbc4.jdbc.SybConnection.a(Unknown Source) > at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(Unknown Source) > at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(Unknown Source) > at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(Unknown Source) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:744) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:730) > at org.jboss.jca.adapters.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:405) > at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:196) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:121) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1] > ... 18 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4643) Add encrypt/decrypt functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4643?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4643. ----------------------------------- Resolution: Done Merged the pull request, but simplified to the binary case and only supporting AES 128 with an explicit initialization vector. We can also address the character case if needed, but that implies choosing more details about the conversion to binary (for example convert to utf-8) and the encrypted string (presumably base64). > Add encrypt/decrypt functions > ----------------------------- > > Key: TEIID-4643 > URL: https://issues.jboss.org/browse/TEIID-4643 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Kylin Soong > Fix For: 9.2 > > > We should add encrypt/decrypt functions similar to the approach of the hash functions added with TEIID-4532 (explicitly named functions for algorithm and probably key length) that are nominally compatible with pgcrypto and other databases. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3836) Create a quick start to demonstrate OData

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3836?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3836: ---------------------------------- Fix Version/s: 9.3 (was: 9.2) > Create a quick start to demonstrate OData > ----------------------------------------- > > Key: TEIID-3836 > URL: https://issues.jboss.org/browse/TEIID-3836 > Project: Teiid > Issue Type: Task > Components: Quick Starts > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Van Halbert > Fix For: 9.3 > > > Add a quick start to demonstrate OData api may helpful for users. > After deploy portfolio-vdb.xml successful, I test with(http://localhost:8080/odata/Portfolio.1/Stocks.StockPrices) return a error: > {code} > TEIID16011 EntitySet "Stocks.StockPrices" is not found; Check the spelling, use modelName.tableName; The table that representing the Entity type must either have a PRIMARY KEY or UNIQUE key(s) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3298) invokeHttp procedure should support returning HTTP Response Code

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3298?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3298: ---------------------------------- Fix Version/s: 9.3 (was: 9.2) > invokeHttp procedure should support returning HTTP Response Code > ---------------------------------------------------------------- > > Key: TEIID-3298 > URL: https://issues.jboss.org/browse/TEIID-3298 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Fix For: 9.3 > > > Currently WS Translator supplied "invokeHttp" procedure only returns the result and as well as the content-type. It should also return response code. > It may be useful to check if there is any other return parameters can be useful too. Like cookie etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3862) Documentation in kit for certain datasources missing

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3862?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3862: ---------------------------------- Fix Version/s: 9.3 (was: 9.2) > Documentation in kit for certain datasources missing > ---------------------------------------------------- > > Key: TEIID-3862 > URL: https://issues.jboss.org/browse/TEIID-3862 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation > Reporter: Ramesh Reddy > Assignee: Van Halbert > Fix For: 9.3 > > > The following data sources do not have documentation under > "docs/teiid/datasources" > where typically a standalone.xml changes and/or CLI scripts are provided. > access > hana > hsql > informix > modeshape > netezza > sybase > teradata > excel > hbase > odata > odata4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4427. ----------------------------------- Fix Version/s: (was: 9.2) Resolution: Incomplete Description Since I couldn't determine a specific regression here, and the issue may be captured more specifically by another JIRA, I'm marking this as resolved. If needed it can be reopened with more information. > Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal > ----------------------------------------------------------------------------------------- > > Key: TEIID-4427 > URL: https://issues.jboss.org/browse/TEIID-4427 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.0 > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Critical > > After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server. > when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year" or "TIMESTAMPDIFF", we are getting the error : Expected integer, but was bigdecimal. > If we go back to Teiid 8.11.3, the same materialized views fetch without any problem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4685) PrestoDB translator - IFNULL is translated as NULLIF

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4685?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4685. ----------------------------------- Resolution: Done Removed locate support and changed ifnull to coalesce > PrestoDB translator - IFNULL is translated as NULLIF > ---------------------------------------------------- > > Key: TEIID-4685 > URL: https://issues.jboss.org/browse/TEIID-4685 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.8.6_3 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.2, 9.1.3 > > > Teiid translates *NULLIF* function to *nullif*. However, those functions have different functionality. Note, this is the case for *COALESCE* with two arguments as well as that function is rewritten to *IFNULL*. > See [PrestoDB doc|https://prestodb.io/docs/current/functions/conditional.html] > {code:sql|title=Query} > SELECT IFNULL(intnum, intkey) FROM BQT1.SmallA > {code} > {code:sql|title=Source command} > SELECT nullif(g_0.intnum, g_0.intkey) FROM smalla AS g_0 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4679) PrestoDB translator - locate function - source specific function has different order of arguments

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4679?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4679. ----------------------------------- Resolution: Done Removed locate support and changed ifnull to coalesce > PrestoDB translator - locate function - source specific function has different order of arguments > ------------------------------------------------------------------------------------------------- > > Key: TEIID-4679 > URL: https://issues.jboss.org/browse/TEIID-4679 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.8.6_3 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.2, 9.1.3 > > > For PrestoDB translator, *locate(x,y)* is translated as *strpos(x,y)* - i.e. *strpos(substring, string)*, but function has different order of arguments - from [PrestoDB documentation|https://prestodb.io/docs/current/functions/string.html] - *strpos(string, substring)* > {code:sql|title=Query} > SELECT StringNum, LOCATE('1', StringNum) FROM BQT1.SmallA > {code} > {code:sql|title=Source-specific command} > SELECT g_0.stringnum, strpos('1', g_0.stringnum) FROM smalla AS g_0 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2017