January 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2605) Optimization substitutes wrong column in where clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2605?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2605. --------------------------------- > Optimization substitutes wrong column in where clause > ----------------------------------------------------- > > Key: TEIID-2605 > URL: https://issues.jboss.org/browse/TEIID-2605 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.1 > Environment: z/OS > Reporter: Jeff Hayes > Assignee: Steven Hawkins > Attachments: query_plan.txt, views.xml > > > Optimization results in a query with a different column in the WHERE clause producing an empty result set. > Full query plan is attached but the beginning and ending queries are shown below. Note that the subject column of the IN clause is SCOPEID but optimization changes it to AUTHID for some reason. > USER COMMAND: > SELECT * FROM SECURITY.SCPXREF AS CHORUS_B WHERE (CHORUS_B.SYSID = 'DE29') AND ((CHORUS_B.SCOPEID IN (SELECT SN5.SCOPEID FROM SECURI > TY.SCPNEXT AS SN5 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN4.SCOPEID FROM SECURITY.SCPNEXT AS SN4 WHERE (SYSID = 'DE29') AND > (NEXTREC IN (SELECT SN3.SCOPEID FROM SECURITY.SCPNEXT AS SN3 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN2.SCOPEID FROM SECURI > TY.SCPNEXT AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))))))))) OR (CHORUS_B.SCOPEID IN (SELECT SN4.SCOPEID FROM SECURIT > Y.SCPNEXT AS SN4 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN3.SCOPEID FROM SECURITY.SCPNEXT AS SN3 WHERE (SYSID = 'DE29') AND > (NEXTREC IN (SELECT SN2.SCOPEID FROM SECURITY.SCPNEXT AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))))))) OR (CHORUS_B.SC > OPEID IN (SELECT SN3.SCOPEID FROM SECURITY.SCPNEXT AS SN3 WHERE (SYSID = 'DE29') AND (NEXTREC IN (SELECT SN2.SCOPEID FROM SECURITY.S > CPNEXT AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))))) OR (CHORUS_B.SCOPEID IN (SELECT SN2.SCOPEID FROM SECURITY.SCPNEX > T AS SN2 WHERE (SYSID = 'DE29') AND (NEXTREC = 'CHRDEPT1'))) OR (CHORUS_B.SCOPEID = 'CHRDEPT1')) > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > AccessNode(10) output=[x.sysid AS sysid, x.scopeid AS authid, x.authid AS scopeid, x.authtype AS authtype] SELECT g_0.SYSID, g_0.SCO > PEID, g_0.AUTHID, g_0.AUTHTYPE FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPXREF AS g_0 WHERE (g_0.SYSID = 'DE29') AND ((g_0.AUTHID IN > (SELECT g_1.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_1 WHERE (g_1.SYSID = 'DE29') AND (g_1.NEXTREC IN (SELECT g_2 > .SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_2 WHERE (g_2.SYSID = 'DE29') AND (g_2.NEXTREC IN (SELECT g_3.SCOPEID FR > OM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_3 WHERE (g_3.SYSID = 'DE29') AND (g_3.NEXTREC IN (SELECT g_4.SCOPEID FROM SECURITY > _CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_4 WHERE (g_4.SYSID = 'DE29') AND (g_4.NEXTREC = 'CHRDEPT1'))))))))) OR (g_0.AUTHID IN (SELECT > g_5.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_5 WHERE (g_5.SYSID = 'DE29') AND (g_5.NEXTREC IN (SELECT g_6.SCOPEI > D FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_6 WHERE (g_6.SYSID = 'DE29') AND (g_6.NEXTREC IN (SELECT g_7.SCOPEID FROM SECU > RITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_7 WHERE (g_7.SYSID = 'DE29') AND (g_7.NEXTREC = 'CHRDEPT1'))))))) OR (g_0.AUTHID IN (SELE > CT g_8.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_8 WHERE (g_8.SYSID = 'DE29') AND (g_8.NEXTREC IN (SELECT g_9.SCOP > EID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_9 WHERE (g_9.SYSID = 'DE29') AND (g_9.NEXTREC = 'CHRDEPT1'))))) OR (g_0.AUTH > ID IN (SELECT g_10.SCOPEID FROM SECURITY_CIA_DB2_D91BPTIB_CIADB01.SCPNEXT AS g_10 WHERE (g_10.SYSID = 'DE29') AND (g_10.NEXTREC = 'C > HRDEPT1'))) OR (g_0.AUTHID = 'CHRDEPT1')) > The view definitions are shown below: > <view name="SCPNEXT"> > <columns> > <column name="sysid" type="varchar"/> > <column name="scopeid" type="varchar"/> > <column name="nextrec" type="varchar"/> > </columns> > <definition> > #if ($db.count("select count(*) from sys.tables where Name='config' and SchemaName = 'security_db'") > 0) > #set ($count = 0) > #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'")) > #if ($db.count("select count(*) from sys.tables where SchemaName = 'SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}'") == 0) > #set ($count = $count + 1) > #end > #end > #if ($count == 0) > SELECT t.sysid, t.scopeid, t.nextrec > FROM ( > #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'")) > SELECT n.sysid, n.scopeid, n.nextrec > FROM SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}.SCPNEXT n > #if( $velocityHasNext ) UNION #end > #end > ) AS t > #end > #end > </definition> > </view> > <view name="SCPXREF"> > <columns> > <column name="sysid" type="varchar"/> > <column name="authid" type="varchar"/> > <column name="scopeid" type="varchar"/> > <column name="authtype" type="varchar"/> > </columns> > <definition> > #if ($db.count("select count(*) from sys.tables where Name='config' and SchemaName = 'security_db'") > 0) > #set ($count = 0) > #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'")) > #if ($db.count("select count(*) from sys.tables where SchemaName = 'SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}'") == 0) > #set ($count = $count + 1) > #end > #end > #if ($count == 0) > SELECT sysid, scopeid, authid, authtype > FROM ( > #foreach($t in $db.query("select DB_TYPE, DB_LOC, DB_QUAL from security_db.config WHERE TYPE = 'CIA'")) > SELECT x.sysid, x.scopeid, x.authid, x.authtype > FROM SECURITY_CIA_${t.DB_TYPE}_${t.DB_LOC}_${t.DB_QUAL}.SCPXREF x > #if( $velocityHasNext ) UNION #end > #end > ) AS t > #end > #end > </definition> > </view> > I guess the best way to test this is to define these views and run the input query with SHOWPLAN=DEBUG and see if the AUTHID substitution is occurring. > Thanks! -- 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

3 months, 2 weeks

2
1
0 / 0

[JBoss JIRA] (TEIIDSB-167) TEIIDSB do release 1.3.1

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-167?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIIDSB-167. ---------------------------------- Fix Version/s: 1.3.1 Resolution: Done > TEIIDSB do release 1.3.1 > ------------------------- > > Key: TEIIDSB-167 > URL: https://issues.redhat.com/browse/TEIIDSB-167 > Project: Teiid Spring Boot > Issue Type: Task > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.1 > > > Update Teiid to 13.0.2 and do a release of 1.3.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-167) TEIIDSB do release 1.3.1

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-167: ------------------------------------ Summary: TEIIDSB do release 1.3.1 Key: TEIIDSB-167 URL: https://issues.redhat.com/browse/TEIIDSB-167 Project: Teiid Spring Boot Issue Type: Task Reporter: Ramesh Reddy Assignee: Ramesh Reddy Update Teiid to 13.0.2 and do a release of 1.3.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5892) Incorrect issue number/link on downloads page

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5892?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5892: ---------------------------------- Original Estimate: 5 minutes Remaining Estimate: 5 minutes Story Points: 0.1 Sprint: DV Sprint 58 > Incorrect issue number/link on downloads page > --------------------------------------------- > > Key: TEIID-5892 > URL: https://issues.redhat.com/browse/TEIID-5892 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Scott Seaton > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 13.1 > > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > On this page: > https://teiid.io/teiid_runtimes/teiid_wildfly/downloads/ > This seems to reference and link to the wrong issue number: > TEIID-5492 added support for an EXPLAIN statement. > Presumably should be this: > https://issues.redhat.com/browse/TEIID-5740 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5892) Incorrect issue number/link on downloads page

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5892?focusedWorklogId=12450013&pag... ] Steven Hawkins logged work on TEIID-5892: ----------------------------------------- Author: Steven Hawkins Created on: 31/Jan/20 2:31 PM Start Date: 31/Jan/20 2:31 PM Worklog Time Spent: 5 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 5 minutes) Time Spent: 5 minutes Worklog Id: (was: 12450013) > Incorrect issue number/link on downloads page > --------------------------------------------- > > Key: TEIID-5892 > URL: https://issues.redhat.com/browse/TEIID-5892 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Scott Seaton > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 13.1 > > Original Estimate: 5 minutes > Time Spent: 5 minutes > Remaining Estimate: 0 minutes > > On this page: > https://teiid.io/teiid_runtimes/teiid_wildfly/downloads/ > This seems to reference and link to the wrong issue number: > TEIID-5492 added support for an EXPLAIN statement. > Presumably should be this: > https://issues.redhat.com/browse/TEIID-5740 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5892) Incorrect issue number/link on downloads page

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5892?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5892. ----------------------------------- Resolution: Done Thanks for catching this. Updating with the 13.0.2 push. > Incorrect issue number/link on downloads page > --------------------------------------------- > > Key: TEIID-5892 > URL: https://issues.redhat.com/browse/TEIID-5892 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Scott Seaton > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 13.1 > > > On this page: > https://teiid.io/teiid_runtimes/teiid_wildfly/downloads/ > This seems to reference and link to the wrong issue number: > TEIID-5492 added support for an EXPLAIN statement. > Presumably should be this: > https://issues.redhat.com/browse/TEIID-5740 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5884) Create common infinispan connection logic

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5884?focusedWorklogId=12450012&pag... ] Steven Hawkins logged work on TEIID-5884: ----------------------------------------- Author: Steven Hawkins Created on: 31/Jan/20 12:57 PM Start Date: 31/Jan/20 12:57 PM Worklog Time Spent: 5 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 4 hours, 30 minutes) Time Spent: 5 hours, 30 minutes (was: 30 minutes) Worklog Id: (was: 12450012) > Create common infinispan connection logic > ----------------------------------------- > > Key: TEIID-5884 > URL: https://issues.redhat.com/browse/TEIID-5884 > Project: Teiid > Issue Type: Task > Components: Infinispan > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Original Estimate: 5 hours > Time Spent: 5 hours, 30 minutes > Remaining Estimate: 0 minutes > > There has been a fork in the infinispan data source logic between teiid and teiid spring boot that could be resolved by moving the common logic into the infinispan api. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5884) Create common infinispan connection logic

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5884?focusedWorklogId=12450011&pag... ] Steven Hawkins logged work on TEIID-5884: ----------------------------------------- Author: Steven Hawkins Created on: 31/Jan/20 12:57 PM Start Date: 31/Jan/20 12:56 PM Worklog Time Spent: 30 minutes Work Description: Updated TSB as well. Issue Time Tracking ------------------- Remaining Estimate: 4 hours, 30 minutes (was: 5 hours) Time Spent: 30 minutes Worklog Id: (was: 12450011) > Create common infinispan connection logic > ----------------------------------------- > > Key: TEIID-5884 > URL: https://issues.redhat.com/browse/TEIID-5884 > Project: Teiid > Issue Type: Task > Components: Infinispan > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Original Estimate: 5 hours > Time Spent: 30 minutes > Remaining Estimate: 4 hours, 30 minutes > > There has been a fork in the infinispan data source logic between teiid and teiid spring boot that could be resolved by moving the common logic into the infinispan api. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5884) Create common infinispan connection logic

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5884?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5884. ----------------------------------- Resolution: Done Created a common base and pulled the changes forward. The spring base connection factory was changed to just return connection, rather than baseconnection - it currently adds no behavior. > Create common infinispan connection logic > ----------------------------------------- > > Key: TEIID-5884 > URL: https://issues.redhat.com/browse/TEIID-5884 > Project: Teiid > Issue Type: Task > Components: Infinispan > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Original Estimate: 5 hours > Remaining Estimate: 5 hours > > There has been a fork in the infinispan data source logic between teiid and teiid spring boot that could be resolved by moving the common logic into the infinispan api. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5884) Create common infinispan connection logic

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5884?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5884: ---------------------------------- Priority: Major (was: Minor) > Create common infinispan connection logic > ----------------------------------------- > > Key: TEIID-5884 > URL: https://issues.redhat.com/browse/TEIID-5884 > Project: Teiid > Issue Type: Task > Components: Infinispan > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Original Estimate: 5 hours > Remaining Estimate: 5 hours > > There has been a fork in the infinispan data source logic between teiid and teiid spring boot that could be resolved by moving the common logic into the infinispan api. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2020