[JBoss JIRA] (TEIID-4901) Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4901?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4901.
-----------------------------------
Resolution: Done
> Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4901
> URL: https://issues.jboss.org/browse/TEIID-4901
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 8.12.10.6_3
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
> Fix For: 9.3, 8.12.x-6.4, 8.12.11.6_3
>
>
> Add the capability to split an independent accessnode into multiple parallel source queries when the number of IN criteria values exceed the translator's MaxInCriteriaSize value. This would be similar handling to what we perform on the dependent side of a dependent join when the number of values exceed the size.
> The background for this request is regarding input to an SAP gateway source which has a MaxInCriteriaSize of 3 due to URL length restrictions. Currently, if 4 values are submitted the full result set is returned to be processed within the Teiid engine.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4722) TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition.
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4722?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4722:
-------------------------------
Git Pull Request: https://github.com/teiid/teiid/pull/956
> TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition.
> -----------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4722
> URL: https://issues.jboss.org/browse/TEIID-4722
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7.10.6_2
> Reporter: Johnathon Lee
> Assignee: Steven Hawkins
> Fix For: 9.2, 9.1.3, 8.7.12.6_2, 8.12.x-6.4, 8.12.11.6_3
>
>
> Assertion failure:
> {code:java}
> ERROR [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue19151) TEIID30019 Unexpected exception for request WrzxYIqVWQ8G.11: java.lang.AssertionError: Assertion failed.
> at org.teiid.core.util.Assertion.failed(Assertion.java:73) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.core.util.Assertion.assertTrue(Assertion.java:68) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.core.util.Assertion.assertTrue(Assertion.java:60) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.query.processor.relational.MergeJoinStrategy.setProcessingSortRight(MergeJoinStrategy.java:367) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.query.processor.relational.DependentAccessNode.prepareNextCommand(DependentAccessNode.java:162) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.query.processor.relational.AccessNode.openInternal(AccessNode.java:259) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:371) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4875) Planning issue with multiple aggregate decompositions through a join tree
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4875?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4875:
-------------------------------
Git Pull Request: https://github.com/teiid/teiid/pull/955
> Planning issue with multiple aggregate decompositions through a join tree
> -------------------------------------------------------------------------
>
> Key: TEIID-4875
> URL: https://issues.jboss.org/browse/TEIID-4875
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.3, 8.12.x-6.4, 9.2.3, 8.12.11.6_3
>
>
> The logic for determining other symbols from aggregates will not work correctly when a staged grouping is initially pushed and another staged grouping is then pushed above a join that is above that location (typically due to join predicates that pull in other groups).
> A query such as:
> SELECT max(t3.e4), max(t2.e4) as s FROM pm1.g1 as t1, pm1.g2 as t2, pm1.g3 as t3, pm1.g4 as t4, pm2.g1 as t5 WHERE t1.e1 = t2.e1 and (t2.e2 = t3.e2 and t1.e3 || t2.e3 = t3.e3) and t3.e3 = t4.e3 and t4.e4 = t5.e4
> With capabilities that disable join pushdown will fail with an assertionerror that a staged grouping symbol cannot be found during the initialization of the parent join node.
> java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
> at org.teiid.core.util.Assertion.failed(Assertion.java:73)
> at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100)
> at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92)
> at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:367)
> at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:133)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:96)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102)
> at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:91)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:226)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4857) Add file metadata such as creation and last modified date to file translator functions
by Marc Shirley (JIRA)
[ https://issues.jboss.org/browse/TEIID-4857?page=com.atlassian.jira.plugin... ]
Marc Shirley commented on TEIID-4857:
-------------------------------------
Steven, no, they are looking for creation timestamp, last modified timestamp, and file size. Their hope was to have this be an extension of the data returned by the file functions (ie, getTextFiles()), but a secondary function that could be used to join the file metadata to the current functionality's results would also work. Their current workaround is to have a UDF that retrieves the last modified date based on the filepath.
> Add file metadata such as creation and last modified date to file translator functions
> --------------------------------------------------------------------------------------
>
> Key: TEIID-4857
> URL: https://issues.jboss.org/browse/TEIID-4857
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
>
> Add file metadata such as creation date and last modified date to the data returned by the file translator functions (getFiles/getTextFiles).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4901) Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4901?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4901:
-------------------------------
Git Pull Request: https://github.com/teiid/teiid/pull/954
> Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4901
> URL: https://issues.jboss.org/browse/TEIID-4901
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 8.12.10.6_3
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
> Fix For: 9.3, 8.12.x-6.4, 8.12.11.6_3
>
>
> Add the capability to split an independent accessnode into multiple parallel source queries when the number of IN criteria values exceed the translator's MaxInCriteriaSize value. This would be similar handling to what we perform on the dependent side of a dependent join when the number of values exceed the size.
> The background for this request is regarding input to an SAP gateway source which has a MaxInCriteriaSize of 3 due to URL length restrictions. Currently, if 4 values are submitted the full result set is returned to be processed within the Teiid engine.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4875) Planning issue with multiple aggregate decompositions through a join tree
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4875?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4875:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1451870, https://bugzilla.redhat.com/show_bug.cgi?id=1444920 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1451870)
Bugzilla Update: Perform
> Planning issue with multiple aggregate decompositions through a join tree
> -------------------------------------------------------------------------
>
> Key: TEIID-4875
> URL: https://issues.jboss.org/browse/TEIID-4875
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.3, 8.12.x-6.4, 9.2.3, 8.12.11.6_3
>
>
> The logic for determining other symbols from aggregates will not work correctly when a staged grouping is initially pushed and another staged grouping is then pushed above a join that is above that location (typically due to join predicates that pull in other groups).
> A query such as:
> SELECT max(t3.e4), max(t2.e4) as s FROM pm1.g1 as t1, pm1.g2 as t2, pm1.g3 as t3, pm1.g4 as t4, pm2.g1 as t5 WHERE t1.e1 = t2.e1 and (t2.e2 = t3.e2 and t1.e3 || t2.e3 = t3.e3) and t3.e3 = t4.e3 and t4.e4 = t5.e4
> With capabilities that disable join pushdown will fail with an assertionerror that a staged grouping symbol cannot be found during the initialization of the parent join node.
> java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
> at org.teiid.core.util.Assertion.failed(Assertion.java:73)
> at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100)
> at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92)
> at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:367)
> at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:133)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:96)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102)
> at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:91)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:226)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months