[JBoss JIRA] (TEIID-5165) Infinispan hotrod translator fails with growing size of returned data
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5165?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5165:
----------------------------------
Fix Version/s: 10.1
(was: 10.x)
> Infinispan hotrod translator fails with growing size of returned data
> ---------------------------------------------------------------------
>
> Key: TEIID-5165
> URL: https://issues.jboss.org/browse/TEIID-5165
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector, Misc. Connectors
> Affects Versions: 8.12.11.6_4
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Priority: Blocker
> Fix For: 8.12.11.6_4, 10.1
>
>
> Infinispan Hotrod translator fails depending on size of data returned.
> I have a table with more than 5000 rows.
> When I issue following query:
> {code:sql}
> SELECT IntKey FROM BQT1.LargeA WHERE Intkey<4095
> {code}
> correct results are returned.
> | 0 |
> | 1 |
> | ... |
> | 4094 |
> When I issue:
> {code:sql}
> SELECT IntKey FROM BQT1.LargeA WHERE Intkey<4096
> {code}
> following exception occurs and no results are returned:
> {code}
> 12:27:56,933 ERROR [org.teiid.CONNECTOR] (Worker8_QueryProcessorQueue279) Connector worker process failed for atomic-request=+VUUR2vieWhT.59.0.46: java.util.NoSuchElementException
> at java.util.ArrayList$Itr.next(ArrayList.java:860) [rt.jar:1.8.0_151]
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.getNextRow(InfinispanResponse.java:106) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.translator.infinispan.hotrod.InfinispanQueryExecution.next(InfinispanQueryExecution.java:142) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:433) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:236) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source) [:1.8.0_151]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at com.sun.proxy.$Proxy79.more(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_151]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
> 12:27:56,941 WARN [org.teiid.PROCESSOR] (Worker7_QueryProcessorQueue282) TEIID30020 Processing exception for request +VUUR2vieWhT.59 'TEIID30504 jdg7-source: null'. Originally TeiidProcessingException ArrayList.java:860. Enable more detailed logging to see the entire stacktrace.
> {code}
> Please note, that this is not affected only by number of rows, also by number of columns. So we're hitting a size limit on whole result set (influence of data type size has not been confirmed).
> This affects also DELETE operation, as selection is part of the operation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIID-5314) usage of environment properties
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5314?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5314:
----------------------------------
Fix Version/s: 10.3.1
11.0
Found out the hard way that sonatype nexus does not allow reployment of artifacts, so I'm immediately releasing a 10.3.1.
> usage of environment properties
> -------------------------------
>
> Key: TEIID-5314
> URL: https://issues.jboss.org/browse/TEIID-5314
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 11.0, 10.3, 10.3.1
>
>
> Places in Teiid that look for system properties should allow for overrides to be specified via environment properties as well. This will make it easier to configure optional behavior on openshift.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIID-5343) Enable absolute URI on context definition of EntitySets when using ODATA
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5343?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-5343:
-------------------------------------
Fix Version/s: 11.0
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Enable absolute URI on context definition of EntitySets when using ODATA
> ------------------------------------------------------------------------
>
> Key: TEIID-5343
> URL: https://issues.jboss.org/browse/TEIID-5343
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Affects Versions: 10.2.1
> Reporter: Rafael Sampaio
> Assignee: Ramesh Reddy
> Fix For: 11.0
>
>
> Hi all you TEIID guys.
> As reported on [OLINGO-1025|https://issues.apache.org/jira/browse/OLINGO-1025], integrating to MS OData consumers (ie. PowerBI/PowerQuery) gives the "should be an absolute Uri" error.
> The proposed solution in the JIRA is implementing a Processor for any given EntityType. Browsing through the code i see TEIID uses the ServiceHandler approach, instead of processor and it also has a Custom JSON Odata Serializer.
> I see that the Default JSON serializer, when serializing entity collections uses the ContextURL to generate the context metadata for the EntityCollection, but by default it does not contain the service root, since it comes from static DataRequest.buildEntitySetContextURL(olingo) method.
> Would be nice if we could choose this behavior through a init param in the odata deployment.
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIID-5314) usage of environment properties
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5314?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5314.
-----------------------------------
Resolution: Done
Added another commit to address the regression in using system properties for dqp core options. This caused a respin of 10.3.
> usage of environment properties
> -------------------------------
>
> Key: TEIID-5314
> URL: https://issues.jboss.org/browse/TEIID-5314
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.3
>
>
> Places in Teiid that look for system properties should allow for overrides to be specified via environment properties as well. This will make it easier to configure optional behavior on openshift.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIID-5345) ClassCastException if multi-column dependent join is pushed to literals
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5345?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5345.
-----------------------------------
Fix Version/s: 10.3
10.2.2
Resolution: Done
Updated the logic to not push dependent predicates that have all constant expressions. It is a TODO to see if we can reverse or otherwise remove the dependent join.
> ClassCastException if multi-column dependent join is pushed to literals
> -----------------------------------------------------------------------
>
> Key: TEIID-5345
> URL: https://issues.jboss.org/browse/TEIID-5345
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.12.6_4
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 10.3, 10.2.2
>
>
> Select without criteria returns - select * from table, If adding criteria on col_CD it fails with ClassCastException[1].
> [1]
> ERROR [org.teiid.PROCESSOR] (Worker133_QueryProcessorQueue5109) TEIID30019 Unexpected exception for request Zplru34y5LCX.5: java.lang.ClassCastException: org.teiid.query.sql.symbol.Constant cannot be cast to org.teiid.query.sql.symbol.Array
> at org.teiid.query.optimizer.relational.rules.CriteriaCapabilityValidatorVisitor$1.visit(CriteriaCapabilityValidatorVisitor.java:894) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.query.sql.lang.DependentSetCriteria.acceptVisitor(DependentSetCriteria.java:161) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.query.optimizer.relational.rules.CriteriaCapabilityValidatorVisitor.canPushLanguageObject(CriteriaCapabilityValidatorVisitor.java:957) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.query.optimizer.relational.rules.CriteriaCapabilityValidatorVisitor.canPushLanguageObject(CriteriaCapabilityValidatorVisitor.java:861) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.query.optimizer.relational.rules.RuleRaiseAccess.canRaiseOverSelect(RuleRaiseAccess.java:512) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.query.optimizer.relational.rules.RulePushSelectCriteria.examinePath(RulePushSelectCriteria.java:442) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.query.optimizer.relational.rules.RulePushSelectCriteria.pushTowardOriginatingNode(RulePushSelectCriteria.java:353) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.query.optimizer.relational.rules.RulePushSelectCriteria.execute(RulePushSelectCriteria.java:116) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:932) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:228) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:159) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:448) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.dqp.internal.process.Request.processRequest(Request.java:476) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:642) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:337) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.12.6_4-redhat-64-2.jar:8.12.12.6_4-redhat-64-2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIID-5232) Add ability to call system functions on VDB Datasource
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5232?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5232.
-----------------------------------
Resolution: Won't Fix
> Add ability to call system functions on VDB Datasource
> ------------------------------------------------------
>
> Key: TEIID-5232
> URL: https://issues.jboss.org/browse/TEIID-5232
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Add ability to call the system function teiid_session_set on a EAP VDB datasource
> When i send :
> select teiid_session_set('project','myProject');
> My session variable is changed only on my vdb. I would want to send this command to my VDB EAP datasource. I need to let my vdb's client the opportunity to call teiid_session_set in one of my datasource dynamically. For now, the only way i have found is putting this on my datasource configuration :
> <new-connection-sql>select teiid_session_set('country','BELGIUM')</new-connection-sql>
> The problem is that this sql request is only called once, at the vdb deployment. I would like to be able to call this request at runtime.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIID-5232) Add ability to call system functions on VDB Datasource
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-5232?page=com.atlassian.jira.plugin... ]
Debbie Steigner commented on TEIID-5232:
----------------------------------------
[~shawkins]Ok, thank you. You can close this feature request then.
> Add ability to call system functions on VDB Datasource
> ------------------------------------------------------
>
> Key: TEIID-5232
> URL: https://issues.jboss.org/browse/TEIID-5232
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Add ability to call the system function teiid_session_set on a EAP VDB datasource
> When i send :
> select teiid_session_set('project','myProject');
> My session variable is changed only on my vdb. I would want to send this command to my VDB EAP datasource. I need to let my vdb's client the opportunity to call teiid_session_set in one of my datasource dynamically. For now, the only way i have found is putting this on my datasource configuration :
> <new-connection-sql>select teiid_session_set('country','BELGIUM')</new-connection-sql>
> The problem is that this sql request is only called once, at the vdb deployment. I would like to be able to call this request at runtime.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIID-5232) Add ability to call system functions on VDB Datasource
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5232?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5232:
---------------------------------------
So the setup is Teiid using VDBs as sources, not vdb imports. Then she wants to call the system function(s) on the source vdbs. However the notion of session continuity is quite problematic here. The user session for the top level vdb would be in no way correlated to the sessions for the source vdbs, which are just pooled connections. If it's just the need to call teiid_session_set, the recommendation would be to add it as a UDF on the source vdbs.
> Add ability to call system functions on VDB Datasource
> ------------------------------------------------------
>
> Key: TEIID-5232
> URL: https://issues.jboss.org/browse/TEIID-5232
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Add ability to call the system function teiid_session_set on a EAP VDB datasource
> When i send :
> select teiid_session_set('project','myProject');
> My session variable is changed only on my vdb. I would want to send this command to my VDB EAP datasource. I need to let my vdb's client the opportunity to call teiid_session_set in one of my datasource dynamically. For now, the only way i have found is putting this on my datasource configuration :
> <new-connection-sql>select teiid_session_set('country','BELGIUM')</new-connection-sql>
> The problem is that this sql request is only called once, at the vdb deployment. I would like to be able to call this request at runtime.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years
[JBoss JIRA] (TEIID-5314) usage of environment properties
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5314?page=com.atlassian.jira.plugin... ]
Steven Hawkins reopened TEIID-5314:
-----------------------------------
There is an issue with creating the properties using the system properties as the default - the later been setting logic does not consider defaults as it just uses a get, rather than getProperty method.
> usage of environment properties
> -------------------------------
>
> Key: TEIID-5314
> URL: https://issues.jboss.org/browse/TEIID-5314
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.3
>
>
> Places in Teiid that look for system properties should allow for overrides to be specified via environment properties as well. This will make it easier to configure optional behavior on openshift.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years