[JBoss JIRA] (TEIID-4947) Error with Salesforce translator if criteria on outer join on a custom table is from the right side table
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4947?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4947.
-----------------------------------
Resolution: Done
Updated the logic to look for __c relationship names to usage as the parent name with __r instead.
> Error with Salesforce translator if criteria on outer join on a custom table is from the right side table
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4947
> URL: https://issues.jboss.org/browse/TEIID-4947
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Affects Versions: 8.7.11.6_2, 8.12.10.6_3
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.3.1
>
>
> Running a left outer join between a parent and child custom table in salesforce results in an error:
> select a.id, a.name, a.LastModifiedDate, b.Order_Recipe_Steps__c, b.name
> from MPRS_Salesforce.Media_Prep_Order_Recipe_Steps__c a left outer join "MPRS_Salesforce"."Recipe_Step_Detail__c" b
> on (a.id = b.Order_Recipe_Steps__c)
> where b.LastModifiedDate >= parsetimestamp('2016-05-04 15:01:03.0', 'yyyy-MM-dd hh:mm:ss.s')
> Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 MPRS_Salesforce: com.sforce.soap.partner.InvalidSObjectFault: INVALID_TYPE:
> Recipe_Step_Detail__c.Catalog_Item__c FROM Recipe_Step_Detail__cs) FROM Media_Prep_Order_Recipe_Steps__c
> ^
> ERROR at Row:1:Column:1137
> Didn't understand relationship 'Recipe_Step_Detail__cs' in FROM part of query call. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names.
> SQLState: 50000
> ErrorCode: 30504
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4947) Error with Salesforce translator if criteria on outer join on a custom table is from the right side table
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4947?page=com.atlassian.jira.plugin... ]
Work on TEIID-4947 started by Steven Hawkins.
---------------------------------------------
> Error with Salesforce translator if criteria on outer join on a custom table is from the right side table
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4947
> URL: https://issues.jboss.org/browse/TEIID-4947
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Affects Versions: 8.7.11.6_2, 8.12.10.6_3
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.3.1
>
>
> Running a left outer join between a parent and child custom table in salesforce results in an error:
> select a.id, a.name, a.LastModifiedDate, b.Order_Recipe_Steps__c, b.name
> from MPRS_Salesforce.Media_Prep_Order_Recipe_Steps__c a left outer join "MPRS_Salesforce"."Recipe_Step_Detail__c" b
> on (a.id = b.Order_Recipe_Steps__c)
> where b.LastModifiedDate >= parsetimestamp('2016-05-04 15:01:03.0', 'yyyy-MM-dd hh:mm:ss.s')
> Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 MPRS_Salesforce: com.sforce.soap.partner.InvalidSObjectFault: INVALID_TYPE:
> Recipe_Step_Detail__c.Catalog_Item__c FROM Recipe_Step_Detail__cs) FROM Media_Prep_Order_Recipe_Steps__c
> ^
> ERROR at Row:1:Column:1137
> Didn't understand relationship 'Recipe_Step_Detail__cs' in FROM part of query call. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names.
> SQLState: 50000
> ErrorCode: 30504
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4950) PostgreSQL Linux ODBC driver v09.06.0100 and newer does not work with Teiid Server 9.1.1
by Steve Boyce (JIRA)
[ https://issues.jboss.org/browse/TEIID-4950?page=com.atlassian.jira.plugin... ]
Steve Boyce commented on TEIID-4950:
------------------------------------
Roger that.
Will set up a test on the current version of Teiid.
Stay tuned.
Thanks!
> PostgreSQL Linux ODBC driver v09.06.0100 and newer does not work with Teiid Server 9.1.1
> ----------------------------------------------------------------------------------------
>
> Key: TEIID-4950
> URL: https://issues.jboss.org/browse/TEIID-4950
> Project: Teiid
> Issue Type: Bug
> Components: ODBC
> Affects Versions: 9.1.1
> Environment: Oracle Linux 7.3
> OBIEE 12c
> unixODBC
> Official PostgreSQL ODBC Drivers
> Reporter: Steve Boyce
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.3.1
>
>
> PostgreSQL ODBC driver v09.06.0100 and newer does not work with Teiid Server 9.1.1
> This is an OBIEE 12c/unixODBC error:
> {noformat}
> [2017-06-06T15:00:48.159+00:00] [OBIS] [ERROR:1] [] [] [ecid: 005KKjYVpflEkJ4_VTS4yc0004Vq0002Lh,0:1] [sik: ssi] [tid: a5dc9700] [nQSError: 16001] ODBC error state: 50000 code: 110 message: [unixODBC]ERROR: TEIID31100 Parsing error: Encountered "[*]SET[*] DateStyle =" at line 1, column 1. [[
> file: server/Query/Execution/DbGateway/Odbc35/../Odbc/Src/SQXDGOdbcConnection.cpp; line: 1009
> Properties: description=ExecutePhysical Exchange; producerID=0x321b5ff8; requestID=0x61ac0002; sessionID=0x61ac0000; userName=weblogic;
> Was expecting: "alter" | "begin" | "call" | "create" | "delete" | "drop" | "exec" | "execute" | "insert" | "merge" ....
> {noformat}
> Looking at the source code for the ODBC drivers, it seems that switching from CC_send_settings to CC_send_query for setting various settings does not work with Teiid.
> {noformat}
> # grep -r -i --include *.c DateStyle psqlodbc-09*
> psqlodbc-09.05.0400/connection.c: CC_send_settings(self, "SET DateStyle = 'ISO';SET extra_float_digits = 2");
> psqlodbc-09.06.0100/connection.c: res = CC_send_query(self, "SET DateStyle = 'ISO';SET extra_float_digits = 2;" ISOLATION_SHOW_QUERY, NULL, 0, NULL);
> psqlodbc-09.06.0200/connection.c: res = CC_send_query(self, "SET DateStyle = 'ISO';SET extra_float_digits = 2;" ISOLATION_SHOW_QUERY, NULL, 0, NULL);
> psqlodbc-09.06.0300/connection.c: res = CC_send_query(self, "SET DateStyle = 'ISO';SET extra_float_digits = 2;" ISOLATION_SHOW_QUERY, NULL, 0, NULL);
> psqlodbc-09.06.0310/connection.c: res = CC_send_query(self, "SET DateStyle = 'ISO';SET extra_float_digits = 2;" ISOLATION_SHOW_QUERY, NULL, 0, NULL);
> {noformat}
> I'm not sure if the bug is with the ODBC driver or this was an intentional change that Postgres Server can deal with and therefore Teiid server should be able to deal with.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4953) JOIN of CTEs fails if one of them is dependent and has window functions with inner DISTINCT in underlying queries
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4953?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4953.
-----------------------------------
Fix Version/s: 9.1.5
9.2.4
Resolution: Done
Added a call to assign with clauses for intermediate with clauses.
> JOIN of CTEs fails if one of them is dependent and has window functions with inner DISTINCT in underlying queries
> -----------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4953
> URL: https://issues.jboss.org/browse/TEIID-4953
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3
> Environment: teiid-9.3.0.Final on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 10.0, 9.1.5, 9.3.1, 9.2.4
>
>
> Running the following script:
> {code:sql|linenumbers|highlight=6,10}
> with
> CTE as (
> select a from test_pg.test_a
> ),
> CTE_WIN_FUNCT as (
> select count(distinct a) over (partition by a) as c from CTE
> ),
> CTE_UNION as (
> select c from CTE_WIN_FUNCT
> union all
> select c from CTE_WIN_FUNCT
> )
> select * from CTE join CTE_UNION on true ;;
> {code}
> leads to the following error message:
> {code}
> 2017-06-07 14:11:09,772 WARN [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue35) QOZCg3H0H+do Connector worker process failed for atomic-request=QOZCg3H0H+do.12.3.2: org.teiid.tra
> nslator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.a FROM CTE AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:365)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:220)
> at com.sun.proxy.$Proxy28.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:266)
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> 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)
> Caused by: org.postgresql.util.PSQLException: relation "cte" does not exist
> Position: 19
> at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
> at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:504)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123)
> ... 18 more
> {code}
> but removing window function completely or just DISTINCT on line 6 makes problem to go away. Removing union all in the "CTE_UNION" eliminates it too.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4896) Two VDB's referencing same teiid_ispn:cache is not using the same cache
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4896?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4896:
-------------------------------
Fix Version/s: 8.12.x-6.4
> Two VDB's referencing same teiid_ispn:cache is not using the same cache
> -----------------------------------------------------------------------
>
> Key: TEIID-4896
> URL: https://issues.jboss.org/browse/TEIID-4896
> Project: Teiid
> Issue Type: Bug
> Components: Infinispan
> Affects Versions: 9.3
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 10.0, 8.12.x-6.4, 9.3.1
>
> Attachments: jdg-remote-cache-ddl-vdb.xml, jdg-remote-cache-registered-pb-vdb.xml
>
>
> I have 2 VDB's where they both reference the same cache using OPTIONS property:
> "teiid_ispn:cache" 'datasourceCache'
> However, when I insert into one VDB, its not seen by the other VDB.
> This was testing out the translators ability to use an already registered protobuf in Infinispan.
> The first VDB (jdg-remote-cache-vdb.xml) was deployed and then inserted and selected the results. This registered the protobuf.
> The second VDB (jdg-remote-cache-registered-pb-vdb.xml) was then deployed and was expecting to be able to read the same cache. The metadata was derived correctly, but it appears that one of the two are using the default cache, not the specified cache.
> I'll attach the vdb's.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4954) The type ispn2.G2 has no property named 'e1'.
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4954?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4954:
-------------------------------
Fix Version/s: (was: 8.12.x-6.4)
> The type ispn2.G2 has no property named 'e1'.
> ---------------------------------------------
>
> Key: TEIID-4954
> URL: https://issues.jboss.org/browse/TEIID-4954
> Project: Teiid
> Issue Type: Bug
> Components: Infinispan
> Affects Versions: 10.0
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Blocker
> Attachments: jdg-remote-cache-ddl-vdb.xml
>
>
> When using the attached VDB, where G1 and G2 look similar, get the following error:
> 09:34:37,202 ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue22) BA7GA3WbC1fa Connector worker process failed for atomic-request=BA7GA3WbC1fa.7.3.1: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=10 returned server error (status=0x85): org.infinispan.objectfilter.ParsingException: ISPN028501: The type ispn2.G2 has no property named 'e1'.
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:68)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:30)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:68)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:53)
> at https://issues.jboss.org/browse/TEIID-4948org.teiid.translator.infinispan...
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.getNextRow(InfinispanResponse.java:86)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4954) The type ispn2.G2 has no property named 'e1'.
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4954?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-4954:
------------------------------------
yes.
> The type ispn2.G2 has no property named 'e1'.
> ---------------------------------------------
>
> Key: TEIID-4954
> URL: https://issues.jboss.org/browse/TEIID-4954
> Project: Teiid
> Issue Type: Bug
> Components: Infinispan
> Affects Versions: 10.0
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Blocker
> Attachments: jdg-remote-cache-ddl-vdb.xml
>
>
> When using the attached VDB, where G1 and G2 look similar, get the following error:
> 09:34:37,202 ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue22) BA7GA3WbC1fa Connector worker process failed for atomic-request=BA7GA3WbC1fa.7.3.1: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=10 returned server error (status=0x85): org.infinispan.objectfilter.ParsingException: ISPN028501: The type ispn2.G2 has no property named 'e1'.
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:68)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:30)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:68)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:53)
> at https://issues.jboss.org/browse/TEIID-4948org.teiid.translator.infinispan...
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.getNextRow(InfinispanResponse.java:86)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4954) The type ispn2.G2 has no property named 'e1'.
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4954?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4954:
-------------------------------------
[~vhalbert2] can we close this as a duplicate then?
> The type ispn2.G2 has no property named 'e1'.
> ---------------------------------------------
>
> Key: TEIID-4954
> URL: https://issues.jboss.org/browse/TEIID-4954
> Project: Teiid
> Issue Type: Bug
> Components: Infinispan
> Affects Versions: 10.0
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 8.12.x-6.4
>
> Attachments: jdg-remote-cache-ddl-vdb.xml
>
>
> When using the attached VDB, where G1 and G2 look similar, get the following error:
> 09:34:37,202 ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue22) BA7GA3WbC1fa Connector worker process failed for atomic-request=BA7GA3WbC1fa.7.3.1: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=10 returned server error (status=0x85): org.infinispan.objectfilter.ParsingException: ISPN028501: The type ispn2.G2 has no property named 'e1'.
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:68)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:30)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:68)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:53)
> at https://issues.jboss.org/browse/TEIID-4948org.teiid.translator.infinispan...
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.getNextRow(InfinispanResponse.java:86)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4680) PrestoDB translator - error executing locate(string, string, int)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4680?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4680:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1456401|https://bugzilla.redhat.com/show_bug.cgi?id=1456401] from ON_QA to ASSIGNED
> PrestoDB translator - error executing locate(string, string, int)
> -----------------------------------------------------------------
>
> Key: TEIID-4680
> URL: https://issues.jboss.org/browse/TEIID-4680
> 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 function *locate(string, string, int)* directly to *strpos(string, string, integer)*, but there is no such function in PrestoDB (see [doc|https://prestodb.io/docs/current/functions/string.html]).
> {code:sql|title=Query}
> SELECT StringNum, LOCATE('1', StringNum, 1) FROM BQT1.SmallA
> {code}
> {code:sql|title=Source command}
> SELECT g_0.stringnum, strpos('1', g_0.stringnum, 1) FROM smalla AS g_0
> {code}
> {code:plain|title=Exception}
> 14:07:37,469 WARN [org.teiid.CONNECTOR] (Worker21_QueryProcessorQueue88) Connector worker process failed for atomic-request=A7WqBzZhsyYM.23.0.21: org.teiid.translator.jdbc.JDBCExecutionException: 1 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT g_0.stringnum, strpos('1', g_0.stringnum, 1) FROM smalla AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364)
> at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) [:1.8.0_92]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_92]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy48.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:266) [rt.jar:1.8.0_92]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> 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) [rt.jar:1.8.0_92]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92]
> Caused by: java.sql.SQLException: Query failed (#20170106_130737_04105_k4ss5): line 1:23: Unexpected parameters (varchar(1), varchar(10), integer) for function strpos. Expected: strpos(varchar, varchar)
> at com.facebook.presto.jdbc.PrestoResultSet.resultsException(PrestoResultSet.java:1799)
> at com.facebook.presto.jdbc.PrestoResultSet.getColumns(PrestoResultSet.java:1747)
> at com.facebook.presto.jdbc.PrestoResultSet.<init>(PrestoResultSet.java:125)
> at com.facebook.presto.jdbc.PrestoStatement.execute(PrestoStatement.java:212)
> at com.facebook.presto.jdbc.PrestoStatement.executeQuery(PrestoStatement.java:69)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:344)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:119) [translator-jdbc-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> ... 17 more
> Caused by: com.facebook.presto.sql.analyzer.SemanticException: line 1:23: Unexpected parameters (varchar(1), varchar(10), integer) for function strpos. Expected: strpos(varchar, varchar)
> at com.facebook.presto.sql.analyzer.ExpressionAnalyzer$Visitor.visitFunctionCall(ExpressionAnalyzer.java:823)
> at com.facebook.presto.sql.analyzer.ExpressionAnalyzer$Visitor.visitFunctionCall(ExpressionAnalyzer.java:254)
> at com.facebook.presto.sql.tree.FunctionCall.accept(FunctionCall.java:109)
> at com.facebook.presto.sql.tree.StackableAstVisitor.process(StackableAstVisitor.java:26)
> at com.facebook.presto.sql.analyzer.ExpressionAnalyzer$Visitor.process(ExpressionAnalyzer.java:273)
> at com.facebook.presto.sql.analyzer.ExpressionAnalyzer.analyze(ExpressionAnalyzer.java:230)
> at com.facebook.presto.sql.analyzer.ExpressionAnalyzer.analyzeExpression(ExpressionAnalyzer.java:1416)
> at com.facebook.presto.sql.analyzer.StatementAnalyzer.analyzeExpression(StatementAnalyzer.java:1791)
> at com.facebook.presto.sql.analyzer.StatementAnalyzer.analyzeSelect(StatementAnalyzer.java:1613)
> at com.facebook.presto.sql.analyzer.StatementAnalyzer.visitQuerySpecification(StatementAnalyzer.java:785)
> at com.facebook.presto.sql.analyzer.StatementAnalyzer.visitQuerySpecification(StatementAnalyzer.java:187)
> at com.facebook.presto.sql.tree.QuerySpecification.accept(QuerySpecification.java:125)
> at com.facebook.presto.sql.tree.AstVisitor.process(AstVisitor.java:27)
> at com.facebook.presto.sql.analyzer.StatementAnalyzer.visitQuery(StatementAnalyzer.java:549)
> at com.facebook.presto.sql.analyzer.StatementAnalyzer.visitQuery(StatementAnalyzer.java:187)
> at com.facebook.presto.sql.tree.Query.accept(Query.java:92)
> at com.facebook.presto.sql.tree.AstVisitor.process(AstVisitor.java:27)
> at com.facebook.presto.sql.analyzer.Analyzer.analyze(Analyzer.java:67)
> at com.facebook.presto.sql.analyzer.Analyzer.analyze(Analyzer.java:59)
> at com.facebook.presto.execution.SqlQueryExecution.doAnalyzeQuery(SqlQueryExecution.java:285)
> at com.facebook.presto.execution.SqlQueryExecution.analyzeQuery(SqlQueryExecution.java:271)
> at com.facebook.presto.execution.SqlQueryExecution.start(SqlQueryExecution.java:229)
> at com.facebook.presto.execution.QueuedExecution.lambda$start$1(QueuedExecution.java:62)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4677) PrestoDB translator - date/time/timestamp values are pushed in Teiid's format ({d/t/ts '...'})
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4677?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4677:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1456401|https://bugzilla.redhat.com/show_bug.cgi?id=1456401] from ON_QA to ASSIGNED
> PrestoDB translator - date/time/timestamp values are pushed in Teiid's format ({d/t/ts '...'})
> ----------------------------------------------------------------------------------------------
>
> Key: TEIID-4677
> URL: https://issues.jboss.org/browse/TEIID-4677
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.8.6_3
> Reporter: Juraj Duráni
> Assignee: Kylin Soong
> Fix For: 9.2
>
>
> Teiid pushes date/time/timestamp values in format *\{d/t/ts '...'\}* to PrestoDB. This is not proper format for PrestoDB. Query \[1\], source-specific command \[2\], exception \[3\].
> {code:sql|title=\[1\]}
> SELECT intkey FROM bqt1.smalla WHERE datevalue = cast('2012-01-01' as date)
> {code}
> {code:sql|title=\[2\]}
> SELECT g_0.intkey FROM smalla AS g_0 WHERE g_0.datevalue = {d '2012-01-01'}
> {code}
> {code:plain|title=\[3\]}
> 12:25:40,369 WARN [org.teiid.CONNECTOR] (Worker9_QueryProcessorQueue51) Connector worker process failed for atomic-request=A7WqBzZhsyYM.11.0.10: org.teiid.translator.jdbc.JDBCExecutionException: 1 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT g_0.intkey FROM smalla AS g_0 WHERE g_0.datevalue = {d '2012-01-01'}]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_92]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_92]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_92]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy48.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:266) [rt.jar:1.8.0_92]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> 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) [rt.jar:1.8.0_92]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92]
> Caused by: java.sql.SQLException: Query failed (#20170106_112540_04080_k4ss5): line 1:60: no viable alternative at input '= {'
> at com.facebook.presto.jdbc.PrestoResultSet.resultsException(PrestoResultSet.java:1799)
> at com.facebook.presto.jdbc.PrestoStatement.execute(PrestoStatement.java:209)
> at com.facebook.presto.jdbc.PrestoStatement.executeQuery(PrestoStatement.java:69)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:344)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:119) [translator-jdbc-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> ... 18 more
> Caused by: com.facebook.presto.sql.parser.ParsingException: line 1:60: no viable alternative at input '= {'
> at com.facebook.presto.sql.parser.SqlParser$1.syntaxError(SqlParser.java:45)
> at org.antlr.v4.runtime.ProxyErrorListener.syntaxError(ProxyErrorListener.java:65)
> at org.antlr.v4.runtime.Parser.notifyErrorListeners(Parser.java:566)
> at org.antlr.v4.runtime.DefaultErrorStrategy.reportNoViableAlternative(DefaultErrorStrategy.java:308)
> at org.antlr.v4.runtime.DefaultErrorStrategy.reportError(DefaultErrorStrategy.java:145)
> at com.facebook.presto.sql.parser.SqlBaseParser.predicate(SqlBaseParser.java:6378)
> at com.facebook.presto.sql.parser.SqlBaseParser.predicated(SqlBaseParser.java:5961)
> at com.facebook.presto.sql.parser.SqlBaseParser.booleanExpression(SqlBaseParser.java:5858)
> at com.facebook.presto.sql.parser.SqlBaseParser.querySpecification(SqlBaseParser.java:3773)
> at com.facebook.presto.sql.parser.SqlBaseParser.queryPrimary(SqlBaseParser.java:3494)
> at com.facebook.presto.sql.parser.SqlBaseParser.queryTerm(SqlBaseParser.java:3306)
> at com.facebook.presto.sql.parser.SqlBaseParser.queryNoWith(SqlBaseParser.java:3162)
> at com.facebook.presto.sql.parser.SqlBaseParser.query(SqlBaseParser.java:2634)
> at com.facebook.presto.sql.parser.SqlBaseParser.statement(SqlBaseParser.java:1294)
> at com.facebook.presto.sql.parser.SqlBaseParser.singleStatement(SqlBaseParser.java:231)
> at com.facebook.presto.sql.parser.SqlParser.invokeParser(SqlParser.java:92)
> at com.facebook.presto.sql.parser.SqlParser.createStatement(SqlParser.java:65)
> at com.facebook.presto.execution.SqlQueryManager.createQuery(SqlQueryManager.java:289)
> at com.facebook.presto.server.StatementResource$Query.<init>(StatementResource.java:309)
> at com.facebook.presto.server.StatementResource.createQuery(StatementResource.java:172)
> at sun.reflect.GeneratedMethodAccessor474.invoke(Unknown Source) [:1.8.0_92]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_92]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92]
> at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
> at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
> at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
> at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
> at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
> at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
> at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
> at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
> at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
> at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
> at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
> at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
> at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
> at io.airlift.http.server.TraceTokenFilter.doFilter(TraceTokenFilter.java:63)
> at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
> at io.airlift.http.server.TimingFilter.doFilter(TimingFilter.java:52)
> at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:395)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1182)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
> at org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:169)
> at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> at org.eclipse.jetty.server.Server.handle(Server.java:523)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
> at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
> at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
> at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
> at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
> at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
> ... 1 more
> Caused by: org.antlr.v4.runtime.NoViableAltException
> at org.antlr.v4.runtime.atn.ParserATNSimulator.noViableAlt(ParserATNSimulator.java:1886)
> at org.antlr.v4.runtime.atn.ParserATNSimulator.execATN(ParserATNSimulator.java:486)
> at org.antlr.v4.runtime.atn.ParserATNSimulator.adaptivePredict(ParserATNSimulator.java:412)
> at com.facebook.presto.sql.parser.SqlBaseParser.predicate(SqlBaseParser.java:6190)
> ... 68 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months