December 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5864) Teiid Query Join Plan Infinite Loop

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5864?page=com.atlassian.jira.plugi... ] Work on TEIID-5864 stopped by Steven Hawkins. --------------------------------------------- > Teiid Query Join Plan Infinite Loop > ----------------------------------- > > Key: TEIID-5864 > URL: https://issues.redhat.com/browse/TEIID-5864 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > > We are getting an infinite loop when executing the below SQL: > {code:java} > SELECT c._COMPTE, > u.CalculatedField, > cl.CHAMPSFCP__VALEUR, > ch_41.CH41__VALEUR, > ch_5.CH5__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CPARTFCP c > LEFT JOIN BInv6BusinessModel.FREPACCOUNTUNION u > ON u.FREP_AFAINB = c._USERNAME > AND u.CalculatedField6 = 'B' > LEFT JOIN BInv6BusinessModel.ClientTypeCode cl > ON c._COMPTE = cl.CHAMPSFCP__COMPTE > LEFT JOIN (SELECT ch._COMPTE AS CH41__COMPTE, > ch._VALEUR AS CH41__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CHAMPSFCP ch > WHERE ch._NUMCHAMPS = 41) ch_41 > ON c._COMPTE = ch_41.CH41__COMPTE > LEFT JOIN (SELECT ch._COMPTE AS CH5__COMPTE, > ch._VALEUR AS CH5__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CHAMPSFCP ch > WHERE ch._NUMCHAMPS = 5) ch_5 > ON c._COMPTE = ch_5.CH5__COMPTE LIMIT 0, 10 > {code} > After debugging, find out that the issue is coming from the class RulePlanOuterJoins method planLeftOuterJoinAssociativityBeforePlanning. > the issue is coming from the below code line, if removed the issue is not reproduced: > {code:java} > changedAny |= val; > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5864) Teiid Query Join Plan Infinite Loop

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5864?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5864: --------------------------------------- So this did not occur on 10.2.1 until you backported a fix? Please reproduce this in 11.2.3+ if possible. Testing just what you have above I can't reproduce this off of master and 10.2.x. If you can still reproduce it, then please provide additional information such as any costing and translator types associated with the tables involved. > Teiid Query Join Plan Infinite Loop > ----------------------------------- > > Key: TEIID-5864 > URL: https://issues.redhat.com/browse/TEIID-5864 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > > We are getting an infinite loop when executing the below SQL: > {code:java} > SELECT c._COMPTE, > u.CalculatedField, > cl.CHAMPSFCP__VALEUR, > ch_41.CH41__VALEUR, > ch_5.CH5__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CPARTFCP c > LEFT JOIN BInv6BusinessModel.FREPACCOUNTUNION u > ON u.FREP_AFAINB = c._USERNAME > AND u.CalculatedField6 = 'B' > LEFT JOIN BInv6BusinessModel.ClientTypeCode cl > ON c._COMPTE = cl.CHAMPSFCP__COMPTE > LEFT JOIN (SELECT ch._COMPTE AS CH41__COMPTE, > ch._VALEUR AS CH41__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CHAMPSFCP ch > WHERE ch._NUMCHAMPS = 41) ch_41 > ON c._COMPTE = ch_41.CH41__COMPTE > LEFT JOIN (SELECT ch._COMPTE AS CH5__COMPTE, > ch._VALEUR AS CH5__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CHAMPSFCP ch > WHERE ch._NUMCHAMPS = 5) ch_5 > ON c._COMPTE = ch_5.CH5__COMPTE LIMIT 0, 10 > {code} > After debugging, find out that the issue is coming from the class RulePlanOuterJoins method planLeftOuterJoinAssociativityBeforePlanning. > the issue is coming from the below code line, if removed the issue is not reproduced: > {code:java} > changedAny |= val; > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5864) Teiid Query Join Plan Infinite Loop

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5864?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5864: ---------------------------------- Component/s: Query Engine > Teiid Query Join Plan Infinite Loop > ----------------------------------- > > Key: TEIID-5864 > URL: https://issues.redhat.com/browse/TEIID-5864 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > > We are getting an infinite loop when executing the below SQL: > {code:java} > SELECT c._COMPTE, > u.CalculatedField, > cl.CHAMPSFCP__VALEUR, > ch_41.CH41__VALEUR, > ch_5.CH5__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CPARTFCP c > LEFT JOIN BInv6BusinessModel.FREPACCOUNTUNION u > ON u.FREP_AFAINB = c._USERNAME > AND u.CalculatedField6 = 'B' > LEFT JOIN BInv6BusinessModel.ClientTypeCode cl > ON c._COMPTE = cl.CHAMPSFCP__COMPTE > LEFT JOIN (SELECT ch._COMPTE AS CH41__COMPTE, > ch._VALEUR AS CH41__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CHAMPSFCP ch > WHERE ch._NUMCHAMPS = 41) ch_41 > ON c._COMPTE = ch_41.CH41__COMPTE > LEFT JOIN (SELECT ch._COMPTE AS CH5__COMPTE, > ch._VALEUR AS CH5__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CHAMPSFCP ch > WHERE ch._NUMCHAMPS = 5) ch_5 > ON c._COMPTE = ch_5.CH5__COMPTE LIMIT 0, 10 > {code} > After debugging, find out that the issue is coming from the class RulePlanOuterJoins method planLeftOuterJoinAssociativityBeforePlanning. > the issue is coming from the below code line, if removed the issue is not reproduced: > {code:java} > changedAny |= val; > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5864) Teiid Query Join Plan Infinite Loop

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5864?page=com.atlassian.jira.plugi... ] Work on TEIID-5864 started by Steven Hawkins. --------------------------------------------- > Teiid Query Join Plan Infinite Loop > ----------------------------------- > > Key: TEIID-5864 > URL: https://issues.redhat.com/browse/TEIID-5864 > Project: Teiid > Issue Type: Bug > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > > We are getting an infinite loop when executing the below SQL: > {code:java} > SELECT c._COMPTE, > u.CalculatedField, > cl.CHAMPSFCP__VALEUR, > ch_41.CH41__VALEUR, > ch_5.CH5__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CPARTFCP c > LEFT JOIN BInv6BusinessModel.FREPACCOUNTUNION u > ON u.FREP_AFAINB = c._USERNAME > AND u.CalculatedField6 = 'B' > LEFT JOIN BInv6BusinessModel.ClientTypeCode cl > ON c._COMPTE = cl.CHAMPSFCP__COMPTE > LEFT JOIN (SELECT ch._COMPTE AS CH41__COMPTE, > ch._VALEUR AS CH41__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CHAMPSFCP ch > WHERE ch._NUMCHAMPS = 41) ch_41 > ON c._COMPTE = ch_41.CH41__COMPTE > LEFT JOIN (SELECT ch._COMPTE AS CH5__COMPTE, > ch._VALEUR AS CH5__VALEUR > FROM OmgModel_Z1rP.OMG.dbo.CHAMPSFCP ch > WHERE ch._NUMCHAMPS = 5) ch_5 > ON c._COMPTE = ch_5.CH5__COMPTE LIMIT 0, 10 > {code} > After debugging, find out that the issue is coming from the class RulePlanOuterJoins method planLeftOuterJoinAssociativityBeforePlanning. > the issue is coming from the below code line, if removed the issue is not reproduced: > {code:java} > changedAny |= val; > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-147) Caching and materialization changes for JDG / OpenShift

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-147?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-147: ---------------------------------------- Either way we may end up having to ignore authorization considerations for now. > Caching and materialization changes for JDG / OpenShift > ------------------------------------------------------- > > Key: TEIIDSB-147 > URL: https://issues.redhat.com/browse/TEIIDSB-147 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core, OpenShift > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > Started this as a higher level issue in Teiid Spring Boot rather than core Teiid since the work won't align well to Teiid 13.1, but some things may need addressed there as well. > Things break down roughly into: > * Single-pod support > ** Define the expectations for how we'll be configured to hit a JDG instance - will it be a user exercise to create if it doesn't exist, will we need to create, will the be a crd strategy for creation, and will it be multi-tenet? There is also the issue / assumption of cache sharing based upon vdb name - is that sufficient for now? > ** validate external materialization to JDG likely using a transactional upsert strategy to avoid issues like TEIID-5436 > * Multi-pod support > ** everything from single-pod support > ** Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication. > ** requires replacing the logic that detect failed materialization loads > ** internal materialization replacement needs to based upon something more like external materialization, but that can be seen as a next step that is turnkey internal materialization to JDG (little to no user setup required) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5798) Mixed PERMISSION GRANTS

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5798?page=com.atlassian.jira.plugi... ] Work on TEIID-5798 stopped by Steven Hawkins. --------------------------------------------- > Mixed PERMISSION GRANTS > ----------------------- > > Key: TEIID-5798 > URL: https://issues.redhat.com/browse/TEIID-5798 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Original Estimate: 6 hours > Time Spent: 4 hours > Remaining Estimate: 1 day, 6 hours > > Hello, > I am currently trying to set a set of permissions on a table/view. Hence a condition on INSERT,UPDATE,DELETE and an unconditioned SELECT. > However, it seems that conditioned and unconditioned GRANT statements do not work together. > {code} > GRANT INSERT,UPDATE,DELETE ON TABLE "my_nutri_diary.UserDefinedProducts_SRC" CONDITION 'UserDefinedProducts_SRC.fkProfile in (SELECT Account.idProfile FROM Account WHERE Account.uuidUser = LEFT(user(), 36) )' TO odata; > GRANT SELECT ON TABLE "my_nutri_diary.UserDefinedProducts_SRC" TO odata; > REVOKE ALTER,EXECUTE ON TABLE "my_nutri_diary.UserDefinedProducts_SRC" FROM odata; > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5863) Regression with TEIID-5737 and socket properties

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5863?focusedWorklogId=12448299&pag... ] Steven Hawkins logged work on TEIID-5863: ----------------------------------------- Author: Steven Hawkins Created on: 05/Dec/19 1:49 PM Start Date: 05/Dec/19 1:49 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 2 hours) Time Spent: 2 hours Worklog Id: (was: 12448299) > Regression with TEIID-5737 and socket properties > ------------------------------------------------ > > Key: TEIID-5863 > URL: https://issues.redhat.com/browse/TEIID-5863 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0, 12.2.2, 12.3.1 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > TEIID-5737 caused properties to no longer be picked up from the teiid-client-settings.properties file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5863) Regression with TEIID-5737 and socket properties

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5863?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5863: ---------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Regression with TEIID-5737 and socket properties > ------------------------------------------------ > > Key: TEIID-5863 > URL: https://issues.redhat.com/browse/TEIID-5863 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0, 12.2.2, 12.3.1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > TEIID-5737 caused properties to no longer be picked up from the teiid-client-settings.properties file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5862) TEIID-5314 does not account for env key name restrictions

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5862?focusedWorklogId=12448298&pag... ] Steven Hawkins logged work on TEIID-5862: ----------------------------------------- Author: Steven Hawkins Created on: 05/Dec/19 1:48 PM Start Date: 05/Dec/19 1:48 PM Worklog Time Spent: 4 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 4 hours) Time Spent: 4 hours Worklog Id: (was: 12448298) > TEIID-5314 does not account for env key name restrictions > ---------------------------------------------------------- > > Key: TEIID-5862 > URL: https://issues.redhat.com/browse/TEIID-5862 > Project: Teiid > Issue Type: Quality Risk > Components: Common > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Original Estimate: 4 hours > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > The logic introduced in TEIID-5314 assumes that env variables can be referenced with existing teiid keys. This was supposed to work with thorntail, but I think that it would have needed to either preprocess the env and populate additional system properties, or otherwise manipulate the env keys. In any event the logic is not sound in general. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5862) TEIID-5314 does not account for env key name restrictions

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5862?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5862: --------------------------------------- I should add that this also switches the property lookup order to match spring boot - system first, then env, then any properties file, etc. > TEIID-5314 does not account for env key name restrictions > ---------------------------------------------------------- > > Key: TEIID-5862 > URL: https://issues.redhat.com/browse/TEIID-5862 > Project: Teiid > Issue Type: Quality Risk > Components: Common > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The logic introduced in TEIID-5314 assumes that env variables can be referenced with existing teiid keys. This was supposed to work with thorntail, but I think that it would have needed to either preprocess the env and populate additional system properties, or otherwise manipulate the env keys. In any event the logic is not sound in general. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2019