[JBoss JIRA] (TEIID-2537) NPE Executing Against REST Web Service Source
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2537?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2537.
---------------------------------
Fix Version/s: 8.4.1
Resolution: Done
Was seeing
{code}
Reason:org.teiid.resource.adapter.ws.WSConnectionImpl$HttpDataSource cannot be cast to java.sql.Blob: java.lang.ClassCastException: org.teiid.resource.adapter.ws.WSConnectionImpl$HttpDataSource cannot be cast to java.sql.Blob
at org.teiid.translator.odata.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:121)
at org.teiid.translator.odata.ODataExecutionFactory.getMetadata(ODataExecutionFactory.java:69)
at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) [teiid-engine-8.4.1.jar:8.4.1]
at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.4.1.jar:8.4.1]
at org.teiid.jboss.VDBService$6.run(VDBService.java:393) [teiid-jboss-integration-8.4.1.jar:8.4.1]
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:806)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:826)
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
{code}
Fixed the as suggested in above comment
> NPE Executing Against REST Web Service Source
> ---------------------------------------------
>
> Key: TEIID-2537
> URL: https://issues.jboss.org/browse/TEIID-2537
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.1
> Reporter: Ted Jones
> Assignee: Steven Hawkins
> Labels: 8.4.Final
> Fix For: 8.4.1, 8.4
>
>
> Using Designer 8.1/Teiid 8.3 and executing against the following:
> http://gw.esworkplace.sap.com/sap/opu/sdata/iwcnt/contact/ContactCollecti...
>
> gives me the following NPE:
> 13:00:28,345 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue25) YH9sbL1HZbxJ TEIID30019 Unexpected exception for request YH9sbL1HZbxJ.6: java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.getOutputParameterValues(BinaryWSProcedureExecution.java:178)
> at org.teiid.dqp.internal.datamgr.ProcedureBatchHandler.getParameterRow(ProcedureBatchHandler.java:86) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:356) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:141) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:467) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:178) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:175) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_45]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_45]
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:264) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_45]
--
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, 5 months
[JBoss JIRA] (TEIID-2537) NPE Executing Against REST Web Service Source
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2537?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reopened TEIID-2537:
---------------------------------
I believe it is typo, it should have been
this.procedure.getArguments().size() > 3
instead of
his.procedure.getArguments().size() > 4
in the BinaryWSProcedureExecution#getOutputParameterValues()
> NPE Executing Against REST Web Service Source
> ---------------------------------------------
>
> Key: TEIID-2537
> URL: https://issues.jboss.org/browse/TEIID-2537
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.1
> Reporter: Ted Jones
> Assignee: Steven Hawkins
> Labels: 8.4.Final
> Fix For: 8.4
>
>
> Using Designer 8.1/Teiid 8.3 and executing against the following:
> http://gw.esworkplace.sap.com/sap/opu/sdata/iwcnt/contact/ContactCollecti...
>
> gives me the following NPE:
> 13:00:28,345 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue25) YH9sbL1HZbxJ TEIID30019 Unexpected exception for request YH9sbL1HZbxJ.6: java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.getOutputParameterValues(BinaryWSProcedureExecution.java:178)
> at org.teiid.dqp.internal.datamgr.ProcedureBatchHandler.getParameterRow(ProcedureBatchHandler.java:86) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:356) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:141) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:467) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:178) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:175) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_45]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_45]
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:264) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_45]
--
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, 5 months
[JBoss JIRA] (TEIID-2067) Global temporary tables
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2067?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2067:
-------------------------------------
ah! the schema part I was missing. thanks.
> Global temporary tables
> -----------------------
>
> Key: TEIID-2067
> URL: https://issues.jboss.org/browse/TEIID-2067
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> Currently, temp tables are scoped to the teiid session (eg, jdbc connection) that created them. I would like temp tables visible to all sessions. It is acceptable and even desirable that temp tables use an external database a la external materialization.
--
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, 5 months
[JBoss JIRA] (TEIID-2067) Global temporary tables
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2067?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2067:
---------------------------------------
The ansi handling for a global temporary table is that it is a proper schema object and is implicitly bound as a new instance to each session upon the first use. So just like all of our other schema entries you will declare them at design/deploy time.
> Global temporary tables
> -----------------------
>
> Key: TEIID-2067
> URL: https://issues.jboss.org/browse/TEIID-2067
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> Currently, temp tables are scoped to the teiid session (eg, jdbc connection) that created them. I would like temp tables visible to all sessions. It is acceptable and even desirable that temp tables use an external database a la external materialization.
--
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, 5 months
[JBoss JIRA] (TEIID-2067) Global temporary tables
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2067?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2067:
-------------------------------------
Why only deploy time? I thought it would be just like session temporary tables with wider scope. Like Matview tables, like matview tables.
> Global temporary tables
> -----------------------
>
> Key: TEIID-2067
> URL: https://issues.jboss.org/browse/TEIID-2067
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> Currently, temp tables are scoped to the teiid session (eg, jdbc connection) that created them. I would like temp tables visible to all sessions. It is acceptable and even desirable that temp tables use an external database a la external materialization.
--
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, 5 months
[JBoss JIRA] (TEIID-2067) Global temporary tables
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2067?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-2067 at 7/19/13 4:03 PM:
--------------------------------------------------------------
Why only deploy time? I thought it would be just like session temporary tables with wider scope. Like Matview tables.
was (Author: rareddy):
Why only deploy time? I thought it would be just like session temporary tables with wider scope. Like Matview tables, like matview tables.
> Global temporary tables
> -----------------------
>
> Key: TEIID-2067
> URL: https://issues.jboss.org/browse/TEIID-2067
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> Currently, temp tables are scoped to the teiid session (eg, jdbc connection) that created them. I would like temp tables visible to all sessions. It is acceptable and even desirable that temp tables use an external database a la external materialization.
--
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, 5 months
[JBoss JIRA] (TEIID-2586) foreign temporary table consistency
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2586?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2586:
---------------------------------------
With the TEIID-2067 change the local keyword was made optional for both the create local temporary and create foreign temporary cases. The rationale is that our interpretation of local differs with the spec, so it's optional if we keep the keyword. It's also unlikely that we'll over the same type of session visibility (such that called procedures can see any session local temp table) and even if we need to offer that functionality it can be done with the declare style syntax used by other databases like db2. I don't believe it's necessary to pull these changes back to 8.4.1.
> foreign temporary table consistency
> -----------------------------------
>
> Key: TEIID-2586
> URL: https://issues.jboss.org/browse/TEIID-2586
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 8.3
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> When creating a foreign temporary table the local keyword is omitted. This was done to cut out some of the verboseness, however it's not consistent with non-foreign tables.
--
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, 5 months