[JBoss JIRA] (TEIID-4664) Arquillian test failed due to new added ftp connector
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4664?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4664:
-------------------------------
Description:
If execute arquillian test
{code}
mvn -Dtest=IntegrationTestDeployment clean test -P arquillian-tests
{code}
getDatasourceTemplateNames will failed due to new added ftp connector
{code}
Results :
Failed tests:
IntegrationTestDeployment.getDatasourceTemplateNames:415 expected:<[teiid, simpledb, teiid-xa, google, h2, salesforce, accumulo, file, ldap, cassandra, teiid-local, solr, teiid-local-xa, salesforce-34, webservice, h2-xa, mongodb]> but was:<[h2, teiid, teiid-local, teiid-local-xa, teiid-xa, h2-xa, accumulo, cassandra, file, ftp, google, ldap, mongodb, salesforce, salesforce-34, simpledb, solr, webservice]>
Tests run: 25, Failures: 1, Errors: 0, Skipped: 1
{code}
was:
Currently rest war generated works fine, but it may throw a duplicate resource error, if restart Server which already have the deployment of rest war:
{code}
10:42:01,080 ERROR [org.jboss.as.controller.management-operation] (Worker2_async-teiid-threads4) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "PortfolioRest_1.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"PortfolioRest_1.war\")]"
10:42:01,087 WARN [org.teiid.RUNTIME] (Worker2_async-teiid-threads4) TEIID50109 Failed to deploy PortfolioRest_1.war: org.teiid.adminapi.AdminProcessingException: TEIID70006 {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"PortfolioRest_1.war\")]"}}
at org.teiid.adminapi.jboss.AdminFactory$AdminImpl.execute(AdminFactory.java:623)
at org.teiid.adminapi.jboss.AdminFactory$AdminImpl.deploy(AdminFactory.java:921)
at org.teiid.jboss.ResteasyEnabler$1.run(ResteasyEnabler.java:94)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282)
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:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
How to reproduce
1. make sure rest quick start work(https://teiid.gitbooks.io/teiid-quickstarts/content/vdb-restservice/)
2. restart server
> Arquillian test failed due to new added ftp connector
> -----------------------------------------------------
>
> Key: TEIID-4664
> URL: https://issues.jboss.org/browse/TEIID-4664
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Affects Versions: 9.2
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.2
>
>
> If execute arquillian test
> {code}
> mvn -Dtest=IntegrationTestDeployment clean test -P arquillian-tests
> {code}
> getDatasourceTemplateNames will failed due to new added ftp connector
> {code}
> Results :
> Failed tests:
> IntegrationTestDeployment.getDatasourceTemplateNames:415 expected:<[teiid, simpledb, teiid-xa, google, h2, salesforce, accumulo, file, ldap, cassandra, teiid-local, solr, teiid-local-xa, salesforce-34, webservice, h2-xa, mongodb]> but was:<[h2, teiid, teiid-local, teiid-local-xa, teiid-xa, h2-xa, accumulo, cassandra, file, ftp, google, ldap, mongodb, salesforce, salesforce-34, simpledb, solr, webservice]>
> Tests run: 25, Failures: 1, Errors: 0, Skipped: 1
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (TEIID-4664) Arquillian test failed due to new added ftp connector
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4664?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4664:
-------------------------------
Summary: Arquillian test failed due to new added ftp connector (was: Failed to deploy generated rest war due to Duplicate resource)
> Arquillian test failed due to new added ftp connector
> -----------------------------------------------------
>
> Key: TEIID-4664
> URL: https://issues.jboss.org/browse/TEIID-4664
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Affects Versions: 9.2
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.2
>
>
> Currently rest war generated works fine, but it may throw a duplicate resource error, if restart Server which already have the deployment of rest war:
> {code}
> 10:42:01,080 ERROR [org.jboss.as.controller.management-operation] (Worker2_async-teiid-threads4) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "PortfolioRest_1.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"PortfolioRest_1.war\")]"
> 10:42:01,087 WARN [org.teiid.RUNTIME] (Worker2_async-teiid-threads4) TEIID50109 Failed to deploy PortfolioRest_1.war: org.teiid.adminapi.AdminProcessingException: TEIID70006 {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"PortfolioRest_1.war\")]"}}
> at org.teiid.adminapi.jboss.AdminFactory$AdminImpl.execute(AdminFactory.java:623)
> at org.teiid.adminapi.jboss.AdminFactory$AdminImpl.deploy(AdminFactory.java:921)
> at org.teiid.jboss.ResteasyEnabler$1.run(ResteasyEnabler.java:94)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> How to reproduce
> 1. make sure rest quick start work(https://teiid.gitbooks.io/teiid-quickstarts/content/vdb-restservice/)
> 2. restart server
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (TEIID-4664) Failed to deploy generated rest war due to Duplicate resource
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4664?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4664:
-------------------------------
Component/s: Server
Fix Version/s: 9.2
Affects Version/s: 9.2
> Failed to deploy generated rest war due to Duplicate resource
> -------------------------------------------------------------
>
> Key: TEIID-4664
> URL: https://issues.jboss.org/browse/TEIID-4664
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Affects Versions: 9.2
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.2
>
>
> Currently rest war generated works fine, but it may throw a duplicate resource error, if restart Server which already have the deployment of rest war:
> {code}
> 10:42:01,080 ERROR [org.jboss.as.controller.management-operation] (Worker2_async-teiid-threads4) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "PortfolioRest_1.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"PortfolioRest_1.war\")]"
> 10:42:01,087 WARN [org.teiid.RUNTIME] (Worker2_async-teiid-threads4) TEIID50109 Failed to deploy PortfolioRest_1.war: org.teiid.adminapi.AdminProcessingException: TEIID70006 {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"PortfolioRest_1.war\")]"}}
> at org.teiid.adminapi.jboss.AdminFactory$AdminImpl.execute(AdminFactory.java:623)
> at org.teiid.adminapi.jboss.AdminFactory$AdminImpl.deploy(AdminFactory.java:921)
> at org.teiid.jboss.ResteasyEnabler$1.run(ResteasyEnabler.java:94)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> How to reproduce
> 1. make sure rest quick start work(https://teiid.gitbooks.io/teiid-quickstarts/content/vdb-restservice/)
> 2. restart server
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (TEIID-4664) Failed to deploy generated rest war due to Duplicate resource
by Kylin Soong (JIRA)
Kylin Soong created TEIID-4664:
----------------------------------
Summary: Failed to deploy generated rest war due to Duplicate resource
Key: TEIID-4664
URL: https://issues.jboss.org/browse/TEIID-4664
Project: Teiid
Issue Type: Quality Risk
Reporter: Kylin Soong
Assignee: Kylin Soong
Currently rest war generated works fine, but it may throw a duplicate resource error, if restart Server which already have the deployment of rest war:
{code}
10:42:01,080 ERROR [org.jboss.as.controller.management-operation] (Worker2_async-teiid-threads4) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "PortfolioRest_1.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"PortfolioRest_1.war\")]"
10:42:01,087 WARN [org.teiid.RUNTIME] (Worker2_async-teiid-threads4) TEIID50109 Failed to deploy PortfolioRest_1.war: org.teiid.adminapi.AdminProcessingException: TEIID70006 {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"PortfolioRest_1.war\")]"}}
at org.teiid.adminapi.jboss.AdminFactory$AdminImpl.execute(AdminFactory.java:623)
at org.teiid.adminapi.jboss.AdminFactory$AdminImpl.deploy(AdminFactory.java:921)
at org.teiid.jboss.ResteasyEnabler$1.run(ResteasyEnabler.java:94)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282)
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:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
How to reproduce
1. make sure rest quick start work(https://teiid.gitbooks.io/teiid-quickstarts/content/vdb-restservice/)
2. restart server
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (TEIID-4656) parseTimestamp issue with Oracle
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-4656?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-4656:
---------------------------------
Fix Version/s: 8.12.9.6_3
> parseTimestamp issue with Oracle
> --------------------------------
>
> Key: TEIID-4656
> URL: https://issues.jboss.org/browse/TEIID-4656
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector, Query Engine
> Affects Versions: 8.12
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.10.6_2, 9.2, 8.12.9.6_3
>
>
> parseTimestamp is pushed as to_timestamp. However TO_TIMESTAMP is not generally valid unless the format string covers the entire string input value otherwise there is an exception about the picture ending.
> This means in general that we cannot pushdown the parseDate/Time/Timestamp operations to oracle as that is behavioral different with the java format routines, which will process just to the end of the format string.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (TEIID-4650) SybaseIQ translator: week function can't be pushed directly
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-4650?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-4650:
------------------------------------
One issue I see with sql anywhere driver is that it requires some native libraries for it to work. So it needs to be installed on the same instance, where teiid is being run. This is a serious limitation of IQ's usage, compared to using just plain Java jConnect driver.
> SybaseIQ translator: week function can't be pushed directly
> -----------------------------------------------------------
>
> Key: TEIID-4650
> URL: https://issues.jboss.org/browse/TEIID-4650
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 9.1.2, 9.2
>
>
> SybaseIQ translator pushes WEEK function calls directly to SAP IQ. SAP IQ doesn't support such function. See [Date and Time Functions docs|http://help.sap.com/saphelp_iq1611_iqrefbb/helpdata/en/a5/2b07be84f2...]
> Query:
> {code:sql}
> SELECT WEEK(dateValue) FROM BQT1.SMALLA;
> {code}
> Pushed source query:
> {code:sql}
> [SELECT week(g_0."datevalue") FROM "bqt-server"."dvqe"."SmallA" AS g_0]
> {code}
> Error in logs:
> {code}
> 08:14:15,830 WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue19) Connector worker process failed for atomic-request=PYp5BTTPF3pK.8.0.2: org.teiid.translator.jdbc.JDBCExecutionException: 504 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT week(g_0."datevalue") FROM "bqt-server"."dvqe"."SmallA" AS g_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: com.sybase.jdbc4.jdbc.SybSQLException: SQL Anywhere Error -265: Procedure 'week' not found
> at com.sybase.jdbc4.tds.Tds.a(Unknown Source)
> at com.sybase.jdbc4.tds.Tds.nextResult(Unknown Source)
> at com.sybase.jdbc4.tds.Tds.getResultSetResult(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]
> ... 18 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months
[JBoss JIRA] (TEIID-4652) SybaseIQ translator: DAYOFYEAR function not pushed correctly
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-4652?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-4652:
------------------------------------
I am using the jConnect driver, which doesn't support the function.
> SybaseIQ translator: DAYOFYEAR function not pushed correctly
> ------------------------------------------------------------
>
> Key: TEIID-4652
> URL: https://issues.jboss.org/browse/TEIID-4652
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> 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)
7 years, 3 months
[JBoss JIRA] (TEIID-4651) SybaseIQ translator: different order of arguments in LOCATE function
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4651?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4651.
-----------------------------------
Fix Version/s: 9.1.2
Resolution: Done
Switched the order of the first two parameters. There is also a limitation documented that their locate function only support a search string of under 256 characters, which may be a later issue.
> SybaseIQ translator: different order of arguments in LOCATE function
> --------------------------------------------------------------------
>
> Key: TEIID-4651
> URL: https://issues.jboss.org/browse/TEIID-4651
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.1.2, 9.2
>
>
> Teiid's and SAP IQ's LOCATE function differs in order of arguments. Translator is pushing the LOCATE function as is into the source, which results in undesirable results. This is critical issue, as the queries seemingly work, but are not producing correct results.
> See [SAP IQ LOCATE function docs|http://help.sap.com/saphelp_iq1611_iqrefbb/helpdata/en/a5/5fae8484f2...]
> Query:
> {code:sql}
> SELECT INTKEY, STRINGNUM, LOCATE(1,STRINGNUM) FROM BQT1.SmallA ORDER BY intkey
> {code}
> being pushed as:
> {code:sql}
> [SELECT g_0."intkey" AS c_0, g_0."stringnum" AS c_1, locate('1', g_0."stringnum") AS c_2 FROM "bqt-server"."dvqe"."SmallA" AS g_0 ORDER BY c_0]
> {code}
> Results in:
> || intkey || stringnum || expr3 ||
> |0 | -24 | 0|
> |1 | <null> | <null>|
> |2 | -22 | 0|
> |3 | -21 | 0|
> |4 | -20 | 0|
> |5 | -19 | 0|
> |6 | -18 | 0|
> |7 | -17 | 0|
> |8 | -16 | 0|
> |9 | -15 | 0|
> |10 | -14 | 0|
> |11 | -13 | 0|
> |12 | -12 | 0|
> |13 | -11 | 0|
> |14 | -10 | 0|
> |15 | -9 | 0|
> |16 | -8 | 0|
> |17 | <null> | <null>|
> |18 | -6 | 0|
> |19 | -5 | 0|
> |20 | -4 | 0|
> |21 | -3 | 0|
> |22 | -2 | 0|
> |23 | -1 | 0|
> |24 | 0 | 0|
> |25 | 1 | 1|
> |26 | 2 | 0|
> |27 | 3 | 0|
> |28 | 4 | 0|
> |29 | 5 | 0|
> |30 | 6 | 0|
> |31 | 7 | 0|
> |32 | 8 | 0|
> |33 | <null> | <null>|
> |34 | 10 | 0|
> |35 | 11 | 0|
> |36 | 12 | 0|
> |37 | 13 | 0|
> |38 | 14 | 0|
> |39 | 15 | 0|
> |40 | 16 | 0|
> |41 | 17 | 0|
> |42 | 18 | 0|
> |43 | 19 | 0|
> |44 | 20 | 0|
> |45 | 21 | 0|
> |46 | 22 | 0|
> |47 | 23 | 0|
> |48 | 24 | 0|
> |49 | <null> | <null> |
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 3 months