[JBoss JIRA] (TEIID-5148) Native: Executing procedures without return values yields an error
by Fábio Franco (JIRA)
Fábio Franco created TEIID-5148:
-----------------------------------
Summary: Native: Executing procedures without return values yields an error
Key: TEIID-5148
URL: https://issues.jboss.org/browse/TEIID-5148
Project: Teiid
Issue Type: Bug
Affects Versions: 9.3.3
Environment: * teiid 9.3.3
* jdbc driver: postgresql-9.4.1212.jre7.jar
* PostgreSQL 9.6.2 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit
* java 1.8.0_141-b15
Reporter: Fábio Franco
Assignee: Steven Hawkins
Executing procedures without return values yields an error when executed via native function from within teiid. The stacktrace is as follows:
{code}
[2017-11-14 11:25:48] [38000] org.postgresql.util.PGobject
[2017-11-14 11:25:48] java.lang.ClassNotFoundException: org.postgresql.util.PGobject
[2017-11-14 11:25:48] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
[2017-11-14 11:25:48] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
[2017-11-14 11:25:48] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
[2017-11-14 11:25:48] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
[2017-11-14 11:25:48] at java.lang.Class.forName0(Native Method)
[2017-11-14 11:25:48] at java.lang.Class.forName(Class.java:348)
[2017-11-14 11:25:48] at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:677)
[2017-11-14 11:25:48] at org.teiid.netty.handler.codec.serialization.CompactObjectInputStream.resolveClass(CompactObjectInputStream.java:112)
[2017-11-14 11:25:48] at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1819)
[2017-11-14 11:25:48] at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1713)
[2017-11-14 11:25:48] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1986)
[2017-11-14 11:25:48] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535)
[2017-11-14 11:25:48] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:422)
[2017-11-14 11:25:48] at org.teiid.client.BatchSerializer$ColumnSerializer.readObject(BatchSerializer.java:552)
[2017-11-14 11:25:48] at org.teiid.client.BatchSerializer$ObjectColumnSerializer.readObject(BatchSerializer.java:283)
[2017-11-14 11:25:48] at org.teiid.client.BatchSerializer$ObjectColumnSerializer.access$2400(BatchSerializer.java:228)
[2017-11-14 11:25:48] at org.teiid.client.BatchSerializer$ArrayColumnSerializer2.readObject(BatchSerializer.java:177)
[2017-11-14 11:25:48] at org.teiid.client.BatchSerializer$ColumnSerializer.readColumn(BatchSerializer.java:543)
[2017-11-14 11:25:48] at org.teiid.client.BatchSerializer.readBatch(BatchSerializer.java:924)
[2017-11-14 11:25:48] at org.teiid.client.ResultsMessage.processResults(ResultsMessage.java:120)
[2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:755)
[2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:65)
[2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:561)
[2017-11-14 11:25:48] at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135)
[2017-11-14 11:25:48] at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40)
[2017-11-14 11:25:48] at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79)
[2017-11-14 11:25:48] at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:285)
[2017-11-14 11:25:48] at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:337)
[2017-11-14 11:25:48] at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
[2017-11-14 11:25:48] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[2017-11-14 11:25:48] at java.lang.reflect.Method.invoke(Method.java:498)
[2017-11-14 11:25:48] at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:98)
[2017-11-14 11:25:48] at com.sun.proxy.$Proxy3.read(Unknown Source)
[2017-11-14 11:25:48] at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:427)
[2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:570)
[2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:423)
[2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:354)
[2017-11-14 11:25:48] at com.intellij.database.remote.jdbc.impl.RemoteStatementImpl.executeQuery(RemoteStatementImpl.java:161)
[2017-11-14 11:25:48] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2017-11-14 11:25:48] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[2017-11-14 11:25:48] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[2017-11-14 11:25:48] at java.lang.reflect.Method.invoke(Method.java:498)
[2017-11-14 11:25:48] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:346)
[2017-11-14 11:25:48] at sun.rmi.transport.Transport$1.run(Transport.java:200)
[2017-11-14 11:25:48] at sun.rmi.transport.Transport$1.run(Transport.java:197)
[2017-11-14 11:25:48] at java.security.AccessController.doPrivileged(Native Method)
[2017-11-14 11:25:48] at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
[2017-11-14 11:25:48] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
[2017-11-14 11:25:48] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
[2017-11-14 11:25:48] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
[2017-11-14 11:25:48] at java.security.AccessController.doPrivileged(Native Method)
[2017-11-14 11:25:48] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
[2017-11-14 11:25:48] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[2017-11-14 11:25:48] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[2017-11-14 11:25:48] at java.lang.Thread.run(Thread.java:745) (no stack trace)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5136) Osisoft translator - NPE when running query with LATERAL JOIN
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIID-5136?page=com.atlassian.jira.plugin... ]
Andrej Šmigala commented on TEIID-5136:
---------------------------------------
[~rareddy] I understand that LATERAL JOIN corresponds to CROSS APPLY in PI, which is very specific thing that needs a TVF (table-valued function) to work.
In my case, the LATERAL JOIN is between to views in PI (no TVF), so CROSS APPLY is not applicable.
In such a case, I would expect teiid to not push the CROSS APPLY and evaluate the LATERAL JOIN internally, as it would with a data source that does not support LATERAL JOIN at all.
> Osisoft translator - NPE when running query with LATERAL JOIN
> -------------------------------------------------------------
>
> Key: TEIID-5136
> URL: https://issues.jboss.org/browse/TEIID-5136
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Fix For: 10.1
>
>
> Running the following 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
> {code}
> results in a NPE in teiid (before sending source src command).
> Stacktrace:
> {noformat}
> Connector worker process failed for atomic-request=vEbs99yd+srV.1.0.1: java.lang.NullPointerException
> at org.teiid.translator.jdbc.pi.PIExecutionFactory.translate(PIExecutionFactory.java:273) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:111) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:106) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.language.visitor.SQLStringVisitor.visit(SQLStringVisitor.java:767) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.language.Select.acceptVisitor(Select.java:110) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:91) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:130) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.translator.jdbc.TranslatedCommand.translateCommand(TranslatedCommand.java:76) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.translator.jdbc.JDBCBaseExecution.translateCommand(JDBCBaseExecution.java:120) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:114) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy79.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_141]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284)
> 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:1149) [rt.jar:1.8.0_141]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5144) Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5144?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5144:
-------------------------------------
[~van.halbert] the above check is already there, I have given to the link to the upstream in the previous comment. [~jstastny] wants more to be done on top to figure out the errors. In connector layer, there is no access to CLI/Admin API. Unless there is some check I can do on the "cache" API above is not a viable option currently. I am inclined to change this is an enhancement rather than a bug.
> Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
> -----------------------------------------------------------------------------
>
> Key: TEIID-5144
> URL: https://issues.jboss.org/browse/TEIID-5144
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector, Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
>
> Infinispan Hotrod translator can't overcome an error in any proto-schema on the JDG server.
> It ends with a message, that there's an issue with a proto-schema. Doesn't say which.
> Note, that this can be completely unrelated proto-schema to Teiid. Then the only solution is to reload JDG, or possibly clear proto-schema cache.
> If Teiid is checking for errors in .errors cache, it should be selective and look only for the newly added proto-schema.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5124) Osisoft translator - Syntax error on datasource for queries with LOCATE
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5124?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5124:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1506285|https://bugzilla.redhat.com/show_bug.cgi?id=1506285] from NEW to MODIFIED
> Osisoft translator - Syntax error on datasource for queries with LOCATE
> -----------------------------------------------------------------------
>
> Key: TEIID-5124
> URL: https://issues.jboss.org/browse/TEIID-5124
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.12.x-6.4
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Fix For: 8.12.x-6.4, 10.1
>
>
> Running a query with LOCATE function causes a syntax error on the PI server:
> {code:sql}
> SELECT INTKEY FROM BQT1.SmallA WHERE LOCATE(2, INTKEY, 1) = 1
> {code}
> is pushed as
> {code:sql}
> SELECT g_0.IntKey AS c_0 FROM dvqe..SmallA AS g_0 WHERE cast(g_0.IntKey AS String)'2'1 = 1
> {code}
> and fails with
> {noformat}
> org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT TOP 100 g_0.IntKey AS c_0 FROM dvqe..SmallA AS g_0 WHERE cast(g_0.IntKey AS String)'2'1 = 1]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy79.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_141]
> 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:1149) [rt.jar:1.8.0_141]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
> Caused by: java.sql.SQLException: [PIOLEDBENT] [SQL Parser] [Line 1:90] Syntax error near '2'
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:360)
> 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.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> ... 18 more
> Caused by: com.osisoft.rdsa.RdsaException: [PIOLEDBENT] [SQL Parser] [Line 1:90] Syntax error near '2'
> at com.osisoft.rdsa.Command.ExecuteReader(Native Method)
> at com.osisoft.rdsa.Command.executeReader(Command.java:79)
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:356)
> ... 20 more
> {noformat}
> Furthermore, query such as
> {code:sql}
> SELECT INTKEY, LOCATE(1, STRINGNUM) FROM BQT1.SmallA
> {code}
> fails on teiid (before push down) with
> {noformat}
> java.lang.IndexOutOfBoundsException: Index: 2, Size: 2
> at java.util.ArrayList.rangeCheck(ArrayList.java:653) [rt.jar:1.8.0_141]
> at java.util.ArrayList.get(ArrayList.java:429) [rt.jar:1.8.0_141]
> at org.teiid.translator.jdbc.pi.PIExecutionFactory$1.translate(PIExecutionFactory.java:89) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.jdbc.JDBCExecutionFactory.translate(JDBCExecutionFactory.java:539) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.jdbc.pi.PIExecutionFactory.translate(PIExecutionFactory.java:260) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:111) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.language.visitor.SQLStringVisitor.visit(SQLStringVisitor.java:834) [teiid-api-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.jdbc.SQLConversionVisitor.visit(SQLConversionVisitor.java:306) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.language.DerivedColumn.acceptVisitor(DerivedColumn.java:47) [teiid-api-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:91) [teiid-api-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:130) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:106) [teiid-api-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.language.visitor.SQLStringVisitor.visit(SQLStringVisitor.java:767) [teiid-api-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.language.Select.acceptVisitor(Select.java:110) [teiid-api-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:91) [teiid-api-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:130) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.jdbc.TranslatedCommand.translateCommand(TranslatedCommand.java:76) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.jdbc.JDBCBaseExecution.translateCommand(JDBCBaseExecution.java:120) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:114) [translator-jdbc-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy79.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_141]
> 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:1149) [rt.jar:1.8.0_141]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5144) Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-5144?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-5144:
------------------------------------
In the 6.x connector, performed the following:
{code}
String errors = metadataCache
.get(ProtobufMetadataManagerConstants.ERRORS_KEY_SUFFIX);
if (errors != null) {
throw new ResourceException(
"Error registering Protobuf schema files:\n" + errors);
}
{code}
and it appears that this same logic still exist in the quickstarts.
> Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
> -----------------------------------------------------------------------------
>
> Key: TEIID-5144
> URL: https://issues.jboss.org/browse/TEIID-5144
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector, Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
>
> Infinispan Hotrod translator can't overcome an error in any proto-schema on the JDG server.
> It ends with a message, that there's an issue with a proto-schema. Doesn't say which.
> Note, that this can be completely unrelated proto-schema to Teiid. Then the only solution is to reload JDG, or possibly clear proto-schema cache.
> If Teiid is checking for errors in .errors cache, it should be selective and look only for the newly added proto-schema.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5144) Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-5144?page=com.atlassian.jira.plugin... ]
Van Halbert edited comment on TEIID-5144 at 11/14/17 8:20 AM:
--------------------------------------------------------------
In the 6.x connector, performed the following:
{code}
String errors = metadataCache
.get(ProtobufMetadataManagerConstants.ERRORS_KEY_SUFFIX);
if (errors != null) {
throw new ResourceException(
"Error registering Protobuf schema files:\n" + errors);
}
{code}
and it appears that this same logic still exist in the 7.1 quickstarts.
was (Author: van.halbert):
In the 6.x connector, performed the following:
{code}
String errors = metadataCache
.get(ProtobufMetadataManagerConstants.ERRORS_KEY_SUFFIX);
if (errors != null) {
throw new ResourceException(
"Error registering Protobuf schema files:\n" + errors);
}
{code}
and it appears that this same logic still exist in the quickstarts.
> Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
> -----------------------------------------------------------------------------
>
> Key: TEIID-5144
> URL: https://issues.jboss.org/browse/TEIID-5144
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector, Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
>
> Infinispan Hotrod translator can't overcome an error in any proto-schema on the JDG server.
> It ends with a message, that there's an issue with a proto-schema. Doesn't say which.
> Note, that this can be completely unrelated proto-schema to Teiid. Then the only solution is to reload JDG, or possibly clear proto-schema cache.
> If Teiid is checking for errors in .errors cache, it should be selective and look only for the newly added proto-schema.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5127) Osisoft translator - MOD fails with non-integer arguments
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5127?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5127:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1506587|https://bugzilla.redhat.com/show_bug.cgi?id=1506587] from NEW to MODIFIED
> Osisoft translator - MOD fails with non-integer arguments
> ---------------------------------------------------------
>
> Key: TEIID-5127
> URL: https://issues.jboss.org/browse/TEIID-5127
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.x-6.4
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Fix For: 8.12.x-6.4, 10.1
>
>
> Query such as
> {code:sql}
> SELECT FloatNum, 11, MOD(FloatNum, 11) FROM BQT1.SmallA
> {code}
> fails on the PI server with
> {noformat}
> com.osisoft.rdsa.RdsaException: [PIOLEDBENT] [SQL Analyzer] [Line 1:34] [%] Overload resolution failed for (Single, Single) argument(s).
> {noformat}
> Similarly for Double arguments. It appears that the modulo operator % is only defined when both arguments are integers (contrary to PI OLEDB Enterprise 2016 User Guide, which states that it is defined for all numeric data types)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5144) Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5144?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-5144:
------------------------------------
[~rareddy] I am asking for such check, otherwise the usage is going to be painful.
What about actually checking the contents of the ".errors" string? Or isn't there such method in hotrod client?
As in jdg cli you can do sth like
{code}
/subsystem=datagrid-infinispan/cache-container=secured:get-proto-schemas-with-errors()
{code}
or
{code}
/subsystem=datagrid-infinispan/cache-container=secured:get-proto-schema-errors(file-name=/the/registered/file.proto)
{code}
and get the keys for the problematic proto-schemas or its contents.
> Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
> -----------------------------------------------------------------------------
>
> Key: TEIID-5144
> URL: https://issues.jboss.org/browse/TEIID-5144
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector, Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
>
> Infinispan Hotrod translator can't overcome an error in any proto-schema on the JDG server.
> It ends with a message, that there's an issue with a proto-schema. Doesn't say which.
> Note, that this can be completely unrelated proto-schema to Teiid. Then the only solution is to reload JDG, or possibly clear proto-schema cache.
> If Teiid is checking for errors in .errors cache, it should be selective and look only for the newly added proto-schema.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5144) Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5144?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5144:
-------------------------------------
[~jstastny] I do not think there is a way to check for errors specifically for a given .proto file, unless you know something. Now I am not sure what you asking me to do.
> Infinispan hotrod translator doesn't overcome error in unrelated proto-schema
> -----------------------------------------------------------------------------
>
> Key: TEIID-5144
> URL: https://issues.jboss.org/browse/TEIID-5144
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector, Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
>
> Infinispan Hotrod translator can't overcome an error in any proto-schema on the JDG server.
> It ends with a message, that there's an issue with a proto-schema. Doesn't say which.
> Note, that this can be completely unrelated proto-schema to Teiid. Then the only solution is to reload JDG, or possibly clear proto-schema cache.
> If Teiid is checking for errors in .errors cache, it should be selective and look only for the newly added proto-schema.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month