[JBoss JIRA] (TEIID-2439) jdbc socket transport support in teiid embedded mode
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2439?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2439:
-------------------------------------
In truly embedded usecase, the user is always building some useful functionality and functional services over and around the Teiid embedded using local jdbc connections. When embedded is exposed remotely, that means you are trying to redo/replicate the functionality of the server that Teiid already provides through JBoss AS in a different host environment. Is this something you can contribute back to community?
> jdbc socket transport support in teiid embedded mode
> ----------------------------------------------------
>
> Key: TEIID-2439
> URL: https://issues.jboss.org/browse/TEIID-2439
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Reporter: Himanshu Kapoor
> Assignee: Steven Hawkins
> Fix For: 8.4, Open To Community
>
>
> As a teiid embedded user there must be JDBC socket transport in embedded mode so that external java application (outside the application server in which teiid embedded has been hosted) can connect to the vdb's using the teiid jdbc driver and can perform operation on it.
> This feature will really help the teiid embedded users to start using this feature in enterprises level applications .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (TEIID-2439) jdbc socket transport support in teiid embedded mode
by Himanshu Kapoor (JIRA)
Himanshu Kapoor created TEIID-2439:
--------------------------------------
Summary: jdbc socket transport support in teiid embedded mode
Key: TEIID-2439
URL: https://issues.jboss.org/browse/TEIID-2439
Project: Teiid
Issue Type: Feature Request
Components: Embedded
Reporter: Himanshu Kapoor
Assignee: Steven Hawkins
Fix For: 8.4, Open To Community
As a teiid embedded user there must be JDBC socket transport in embedded mode so that external java application (outside the application server in which teiid embedded has been hosted) can connect to the vdb's using the teiid jdbc driver and can perform operation on it.
This feature will really help the teiid embedded users to start using this feature in enterprises level applications .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (TEIID-2438) Hive Connector not working in Teiid 8
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2438?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2438.
-----------------------------------
Resolution: Done
We needed to handle the null case as that is what we mapped empty strings to.
> Hive Connector not working in Teiid 8
> -------------------------------------
>
> Key: TEIID-2438
> URL: https://issues.jboss.org/browse/TEIID-2438
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.3
> Environment: Any
> Reporter: Filip Nguyen
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> Hive Connector is not working. It throws exception [2] when the query is submitted. Bug was introduced in commit 98456d89aa6c04028dbf971bddc322b3e3a3978b in patch for [1].
> Problem is metadata loading. The HiveMetadataProcessor adds strings "null" around table names because the patch [1] calls common JDBCConnector's addTable. That method then uses "quote" field (which is null) to quote the table name and sets this to nameInSource property.
> [1] https://issues.jboss.org/browse/TEIID-2281
> [2]
> {code:title=Exception|borderStyle=solid}
> 14:17:16,870 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=s9z3Rn3JAr7e.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 10 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.col FROM nullmyfilesnull g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:257) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:457) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:177) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:174) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_07]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_07]
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:118) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:250) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: java.sql.SQLException: Query returned non-zero code: 10, cause: FAILED: Error in semantic analysis: Line 1:20 Table not found 'nullmyfilesnull'
> at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:177)
> at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeQuery(HivePreparedStatement.java:140)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84)
> ... 13 more
> Caused by: HiveServerException(message:Query returned non-zero code: 10, cause: FAILED: Error in semantic analysis: Line 1:20 Table not found 'nullmyfilesnull', errorCode:10, SQLState:42000)
> at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1494)
> at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1480)
> at org.apache.hadoop.hive.service.ThriftHive$execute_result.read(ThriftHive.java:1430)
> at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
> at org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:116)
> at org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:103)
> at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:175)
> ... 16 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (TEIID-2438) Hive Connector not working in Teiid 8
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2438?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2438:
----------------------------------
Fix Version/s: 8.4
Priority: Major (was: Blocker)
Workaround Description: Set the importer.quoteNameInSource property to false on the model.
Workaround: Workaround Exists
> Hive Connector not working in Teiid 8
> -------------------------------------
>
> Key: TEIID-2438
> URL: https://issues.jboss.org/browse/TEIID-2438
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.3
> Environment: Any
> Reporter: Filip Nguyen
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> Hive Connector is not working. It throws exception [2] when the query is submitted. Bug was introduced in commit 98456d89aa6c04028dbf971bddc322b3e3a3978b in patch for [1].
> Problem is metadata loading. The HiveMetadataProcessor adds strings "null" around table names because the patch [1] calls common JDBCConnector's addTable. That method then uses "quote" field (which is null) to quote the table name and sets this to nameInSource property.
> [1] https://issues.jboss.org/browse/TEIID-2281
> [2]
> {code:title=Exception|borderStyle=solid}
> 14:17:16,870 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=s9z3Rn3JAr7e.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 10 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.col FROM nullmyfilesnull g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:257) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:457) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:177) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:174) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_07]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_07]
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:118) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:250) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: java.sql.SQLException: Query returned non-zero code: 10, cause: FAILED: Error in semantic analysis: Line 1:20 Table not found 'nullmyfilesnull'
> at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:177)
> at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeQuery(HivePreparedStatement.java:140)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84)
> ... 13 more
> Caused by: HiveServerException(message:Query returned non-zero code: 10, cause: FAILED: Error in semantic analysis: Line 1:20 Table not found 'nullmyfilesnull', errorCode:10, SQLState:42000)
> at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1494)
> at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1480)
> at org.apache.hadoop.hive.service.ThriftHive$execute_result.read(ThriftHive.java:1430)
> at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
> at org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:116)
> at org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:103)
> at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:175)
> ... 16 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (TEIID-2438) Hive Connector not working in Teiid 8
by Filip Nguyen (JIRA)
Filip Nguyen created TEIID-2438:
-----------------------------------
Summary: Hive Connector not working in Teiid 8
Key: TEIID-2438
URL: https://issues.jboss.org/browse/TEIID-2438
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 8.3
Environment: Any
Reporter: Filip Nguyen
Assignee: Steven Hawkins
Priority: Blocker
Hive Connector is not working. It throws exception [2] when the query is submitted. Bug was introduced in commit 98456d89aa6c04028dbf971bddc322b3e3a3978b in patch for [1].
Problem is metadata loading. The HiveMetadataProcessor adds strings "null" around table names because the patch [1] calls common JDBCConnector's addTable. That method then uses "quote" field (which is null) to quote the table name and sets this to nameInSource property.
[1] https://issues.jboss.org/browse/TEIID-2281
[2]
{code:title=Exception|borderStyle=solid}
14:17:16,870 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=s9z3Rn3JAr7e.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 10 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.col FROM nullmyfilesnull g_0]
at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:257) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:457) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:177) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:174) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_07]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_07]
at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:118) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:250) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
Caused by: java.sql.SQLException: Query returned non-zero code: 10, cause: FAILED: Error in semantic analysis: Line 1:20 Table not found 'nullmyfilesnull'
at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:177)
at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeQuery(HivePreparedStatement.java:140)
at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84)
... 13 more
Caused by: HiveServerException(message:Query returned non-zero code: 10, cause: FAILED: Error in semantic analysis: Line 1:20 Table not found 'nullmyfilesnull', errorCode:10, SQLState:42000)
at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1494)
at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1480)
at org.apache.hadoop.hive.service.ThriftHive$execute_result.read(ThriftHive.java:1430)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:116)
at org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:103)
at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:175)
... 16 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] (TEIID-2437) Issuing query against SYS.VirtualDatabases causes SingleInstanceCommunicationException
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2437?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2437.
-----------------------------------
Resolution: Done
changed the datatiermanager to supply a string value instead
> Issuing query against SYS.VirtualDatabases causes SingleInstanceCommunicationException
> --------------------------------------------------------------------------------------
>
> Key: TEIID-2437
> URL: https://issues.jboss.org/browse/TEIID-2437
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.4
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.4
>
>
> Issuing query: select * from SYS.VirtualDatabases using Squirrel produces this error on client:
> Error: org.teiid.net.socket.SingleInstanceCommunicationException
> SQLState: 08S01
> ErrorCode: 0
> The server log shows this error:
> 12:34:41,665 ERROR [org.teiid.TRANSPORT] (New I/O worker #1) Unhandled exception, closing client instance: org.teiid.core.TeiidRuntimeException: TEIID20001 The modeled datatype string for column 1 doesn't match the runtime type "java.lang.Integer". Please ensure that the column's modeled datatype matches the expected data.
> at org.teiid.client.BatchSerializer.writeBatch(BatchSerializer.java:732) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.client.ResultsMessage.writeExternal(ResultsMessage.java:291) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) [rt.jar:1.7.0_13]
> at org.teiid.net.socket.Message.writeExternal(Message.java:56) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) [rt.jar:1.7.0_13]
> at org.teiid.transport.ObjectEncoder.handleDownstream(ObjectEncoder.java:115) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.jboss.netty.channel.Channels.write(Channels.java:704) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.Channels.write(Channels.java:671) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]
> at org.teiid.transport.SSLAwareChannelHandler$ObjectChannelImpl.write(SSLAwareChannelHandler.java:94) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.transport.SocketClientInstance.send(SocketClientInstance.java:82) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.transport.ServerWorkItem.sendResult(ServerWorkItem.java:135) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.transport.ServerWorkItem$1.onCompletion(ServerWorkItem.java:105) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:130) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:37) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.sendResultsIfNeeded(RequestWorkItem.java:785) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:583) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:191) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:166) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:400) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:296) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:224) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:253) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2432:
---------------------------------------
I'm not sure the waiting status is needed for the entire vdb. It seems like you just need/want a clearer indication that a particular error message on a model means that the source is unavailable or otherwise erroring out. Perhaps that means loading statuses for each model to see which ones are waiting vs. those that are just taking a long time (due to a custom repository or large source crawl) vs. those that are already done.
> Dynamic VDB isLoading state doesnt change on fail
> -------------------------------------------------
>
> Key: TEIID-2432
> URL: https://issues.jboss.org/browse/TEIID-2432
> Project: Teiid
> Issue Type: Feature Request
> Components: AdminApi
> Affects Versions: 8.2
> Reporter: Mark Drilling
> Assignee: Ramesh Reddy
>
> I am deploying a dynamic VDB and polling the isLoading state to determine when the VDB deployment is finished.
> In my case the VDB dataSource is not available. I can see in the server log that the deployment fails immediately, but the isLoading state remains true.
> Is this in error, or what status should we be checking?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (TEIID-2428) Sybase15 - jconn4-26502 driver behaviour causes exception in Teiid server
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2428?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2428.
-----------------------------------
Resolution: Done
updated the logic to not set the fetchsize by default - it will if set as the jtds driver.
> Sybase15 - jconn4-26502 driver behaviour causes exception in Teiid server
> -------------------------------------------------------------------------
>
> Key: TEIID-2428
> URL: https://issues.jboss.org/browse/TEIID-2428
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.3
> Reporter: Warren Gibson
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> If the following queries are all submitted several times against a Teiid 8.3 Beta3 server eventually the following exception will be produced and the sybase source becomes unresponsive to additional queries.
> SELECT INTKEY FROM BQT1.SmallA ORDER BY INTKEY LIMIT 45, 10;
> SELECT INTKEY FROM BQT1.SmallA ORDER BY INTKEY LIMIT 50, 10;
> SELECT INTKEY FROM BQT1.SmallA ORDER BY INTKEY LIMIT 55, 10;
> SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY OFFSET 45 ROWS;
> SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY FETCH FIRST ROW ONLY;
> SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY FETCH FIRST 5 ROW ONLY;
> SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY FETCH FIRST 5 ROWS ONLY;
> Further analysis by engineering (using the above queries) has revealed that with asynch processing the close of one resultset can cause a null pointer exception for a different resultset close (that's on a different connection!) This behavior was found in jconn3 and jconn4 drivers.
> Log Exception:
> 17:29:47,203 WARN [org.teiid.CONNECTOR] (Worker23_QueryProcessorQueue16357) Connector worker process failed for atomic-request=7d35ZSARrCwK.2906.1.3307: org.teiid.translator.TranslatorException: Unexpected exception while translating results: The result set is closed.
> at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:108)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:316) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:141) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:467) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:178) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:175) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0]
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:253) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]
> Caused by: java.sql.SQLException: The result set is closed.
> at org.jboss.jca.adapters.jdbc.WrappedResultSet.checkState(WrappedResultSet.java:4081)
> at org.jboss.jca.adapters.jdbc.WrappedResultSet.getInt(WrappedResultSet.java:1044)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.retrieveValue(JDBCExecutionFactory.java:867)
> at org.teiid.translator.jdbc.sybase.BaseSybaseExecutionFactory.retrieveValue(BaseSybaseExecutionFactory.java:118)
> at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:101)
> ... 14 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (TEIID-2427) Include nested message in processing exception warnings
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2427?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2427.
-----------------------------------
Resolution: Done
Refined the processing exception message to be more concise and include the underlying message as well.
> Include nested message in processing exception warnings
> -------------------------------------------------------
>
> Key: TEIID-2427
> URL: https://issues.jboss.org/browse/TEIID-2427
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> In many instances (especially with initial non-teiid exceptions) the original intent of the exception is not clear in the warning logged by teiid because only the top level message is there (for teiid exceptions we'll typically have the code chain, but that's not necessarily useful for the user). The root message would also be helpful so that detail logging is not needed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (TEIID-2437) Issuing query against SYS.VirtualDatabases causes SingleInstanceCommunicationException
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2437?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2437:
----------------------------------
Fix Version/s: 8.4
Affects Version/s: 7.4
(was: 8.3)
Workaround Description: use cast(cast(version as object) as string)
Component/s: Query Engine
(was: Server)
There is a mismatch between the metadata and the DatatierManager as the latter is returning an integer in the place of string column. This looks like it has been that way at least since 7.4.
> Issuing query against SYS.VirtualDatabases causes SingleInstanceCommunicationException
> --------------------------------------------------------------------------------------
>
> Key: TEIID-2437
> URL: https://issues.jboss.org/browse/TEIID-2437
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.4
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.4
>
>
> Issuing query: select * from SYS.VirtualDatabases using Squirrel produces this error on client:
> Error: org.teiid.net.socket.SingleInstanceCommunicationException
> SQLState: 08S01
> ErrorCode: 0
> The server log shows this error:
> 12:34:41,665 ERROR [org.teiid.TRANSPORT] (New I/O worker #1) Unhandled exception, closing client instance: org.teiid.core.TeiidRuntimeException: TEIID20001 The modeled datatype string for column 1 doesn't match the runtime type "java.lang.Integer". Please ensure that the column's modeled datatype matches the expected data.
> at org.teiid.client.BatchSerializer.writeBatch(BatchSerializer.java:732) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.client.ResultsMessage.writeExternal(ResultsMessage.java:291) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) [rt.jar:1.7.0_13]
> at org.teiid.net.socket.Message.writeExternal(Message.java:56) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) [rt.jar:1.7.0_13]
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) [rt.jar:1.7.0_13]
> at org.teiid.transport.ObjectEncoder.handleDownstream(ObjectEncoder.java:115) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.jboss.netty.channel.Channels.write(Channels.java:704) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.Channels.write(Channels.java:671) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1]
> at org.teiid.transport.SSLAwareChannelHandler$ObjectChannelImpl.write(SSLAwareChannelHandler.java:94) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.transport.SocketClientInstance.send(SocketClientInstance.java:82) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.transport.ServerWorkItem.sendResult(ServerWorkItem.java:135) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.transport.ServerWorkItem$1.onCompletion(ServerWorkItem.java:105) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:130) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:37) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.sendResultsIfNeeded(RequestWorkItem.java:785) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:583) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:191) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:166) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:400) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:296) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:224) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:253) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years