January 2019 - 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

1 week, 4 days

2
1
0 / 0

[JBoss JIRA] (TEIID-5639) Auto-generated REST war creates different context than Designer Generated REST war

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5639?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5639: --------------------------------------- [~dsteigne] I'd say this is an issue with Designer. The Teiid side is documented as expecting uri parameters in curly braces - http://teiid.github.io/teiid-documents/master/content/reference/REST_Serv... - which matches the jax rs specification. > Auto-generated REST war creates different context than Designer Generated REST war > ---------------------------------------------------------------------------------- > > Key: TEIID-5639 > URL: https://issues.jboss.org/browse/TEIID-5639 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.16.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Attachments: AutoGenSwaggar.png, DesignerGenSwagger.png, WW-vdb.xml > > > Have a REST procedure with 3 optional parameters and have the REST:URI set to testget&inA&inB&inC, the Designer Generated War takes the REST:URI of testget&inA&inB&inC and drops the params, so you see in the Swagger UI the operation is just /AAA/testget, so the Request URL is http://localhost:8080/WW/AAA/testget?inA=abc&inC=def but the auto-generated war file doesn't drop the params from the REST:URI and it shows as /AAA/testget&inA&inB&inC so the actual Request URL would be http://localhost:8080/WW_1/AAA/testget&inA&inB&inC?inA=abc&inC=def. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4051) Swagger metadata includes internal java constructs

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4051: --------------------------------------- A related issue - https://github.com/swagger-api/swagger-codegen/issues/4831 It looks like the swagger utilities still don't understand StreamingOutput > Swagger metadata includes internal java constructs > -------------------------------------------------- > > Key: TEIID-4051 > URL: https://issues.jboss.org/browse/TEIID-4051 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > From IntegrationTestRestWarGeneration the swagger metadata includes definitions for Statement, ResultSet, StreamingOutput, etc.: > ... > InputStream: > type: "object" > Statement: > type: "object" > properties: > queryTimeout: > type: "integer" > format: "int32" > closed: > type: "boolean" > default: false > resultSet: > $ref: "#/definitions/ResultSet" > ... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5592) Update or deprecate teiid-quickstarts

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5592?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5592: --------------------------------------- The alternative is to deprecate - on the website and in the repo make it clear that it was written for older Teiids and JDV. > Update or deprecate teiid-quickstarts > ------------------------------------- > > Key: TEIID-5592 > URL: https://issues.jboss.org/browse/TEIID-5592 > Project: Teiid > Issue Type: Quality Risk > Components: Quick Starts > Reporter: Steven Hawkins > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > The last update to the quickstarts was for Teiid 10 - which should have been largely compatible with Teiid 11. However this should be reviewed and updated for Teiid 11 - or we should deprecate them and update teiid.io appropriately. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5640) Don't provide access to system schema over odata

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5640: ------------------------------------- Summary: Don't provide access to system schema over odata Key: TEIID-5640 URL: https://issues.jboss.org/browse/TEIID-5640 Project: Teiid Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.1 We now create all of the edm metadata at once - including for system schema - but we should not allow that by default. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5639) Auto-generated REST war creates different context than Designer Generated REST war

by Debbie Steigner (Jira)

[ https://issues.jboss.org/browse/TEIID-5639?page=com.atlassian.jira.plugin... ] Debbie Steigner updated TEIID-5639: ----------------------------------- Attachment: WW-vdb.xml > Auto-generated REST war creates different context than Designer Generated REST war > ---------------------------------------------------------------------------------- > > Key: TEIID-5639 > URL: https://issues.jboss.org/browse/TEIID-5639 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.16.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Attachments: AutoGenSwaggar.png, DesignerGenSwagger.png, WW-vdb.xml > > > Have a REST procedure with 3 optional parameters and have the REST:URI set to testget&inA&inB&inC, the Designer Generated War takes the REST:URI of testget&inA&inB&inC and drops the params, so you see in the Swagger UI the operation is just /AAA/testget, so the Request URL is http://localhost:8080/WW/AAA/testget?inA=abc&inC=def but the auto-generated war file doesn't drop the params from the REST:URI and it shows as /AAA/testget&inA&inB&inC so the actual Request URL would be http://localhost:8080/WW_1/AAA/testget&inA&inB&inC?inA=abc&inC=def. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5639) Auto-generated REST war creates different context than Designer Generated REST war

by Debbie Steigner (Jira)

[ https://issues.jboss.org/browse/TEIID-5639?page=com.atlassian.jira.plugin... ] Debbie Steigner updated TEIID-5639: ----------------------------------- Attachment: AutoGenSwaggar.png > Auto-generated REST war creates different context than Designer Generated REST war > ---------------------------------------------------------------------------------- > > Key: TEIID-5639 > URL: https://issues.jboss.org/browse/TEIID-5639 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.16.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Attachments: AutoGenSwaggar.png, DesignerGenSwagger.png > > > Have a REST procedure with 3 optional parameters and have the REST:URI set to testget&inA&inB&inC, the Designer Generated War takes the REST:URI of testget&inA&inB&inC and drops the params, so you see in the Swagger UI the operation is just /AAA/testget, so the Request URL is http://localhost:8080/WW/AAA/testget?inA=abc&inC=def but the auto-generated war file doesn't drop the params from the REST:URI and it shows as /AAA/testget&inA&inB&inC so the actual Request URL would be http://localhost:8080/WW_1/AAA/testget&inA&inB&inC?inA=abc&inC=def. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5592) Update or deprecate teiid-quickstarts

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5592?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-5592: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Update or deprecate teiid-quickstarts > ------------------------------------- > > Key: TEIID-5592 > URL: https://issues.jboss.org/browse/TEIID-5592 > Project: Teiid > Issue Type: Quality Risk > Components: Quick Starts > Reporter: Steven Hawkins > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > The last update to the quickstarts was for Teiid 10 - which should have been largely compatible with Teiid 11. However this should be reviewed and updated for Teiid 11 - or we should deprecate them and update teiid.io appropriately. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5639) Auto-generated REST war creates different context than Designer Generated REST war

by Debbie Steigner (Jira)

[ https://issues.jboss.org/browse/TEIID-5639?page=com.atlassian.jira.plugin... ] Debbie Steigner updated TEIID-5639: ----------------------------------- Attachment: DesignerGenSwagger.png > Auto-generated REST war creates different context than Designer Generated REST war > ---------------------------------------------------------------------------------- > > Key: TEIID-5639 > URL: https://issues.jboss.org/browse/TEIID-5639 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.16.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Attachments: AutoGenSwaggar.png, DesignerGenSwagger.png > > > Have a REST procedure with 3 optional parameters and have the REST:URI set to testget&inA&inB&inC, the Designer Generated War takes the REST:URI of testget&inA&inB&inC and drops the params, so you see in the Swagger UI the operation is just /AAA/testget, so the Request URL is http://localhost:8080/WW/AAA/testget?inA=abc&inC=def but the auto-generated war file doesn't drop the params from the REST:URI and it shows as /AAA/testget&inA&inB&inC so the actual Request URL would be http://localhost:8080/WW_1/AAA/testget&inA&inB&inC?inA=abc&inC=def. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5639) Auto-generated REST war creates different context than Designer Generated REST war

by Debbie Steigner (Jira)

Debbie Steigner created TEIID-5639: -------------------------------------- Summary: Auto-generated REST war creates different context than Designer Generated REST war Key: TEIID-5639 URL: https://issues.jboss.org/browse/TEIID-5639 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.12.16.6_4 Reporter: Debbie Steigner Assignee: Steven Hawkins Attachments: AutoGenSwaggar.png, DesignerGenSwagger.png Have a REST procedure with 3 optional parameters and have the REST:URI set to testget&inA&inB&inC, the Designer Generated War takes the REST:URI of testget&inA&inB&inC and drops the params, so you see in the Swagger UI the operation is just /AAA/testget, so the Request URL is http://localhost:8080/WW/AAA/testget?inA=abc&inC=def but the auto-generated war file doesn't drop the params from the REST:URI and it shows as /AAA/testget&inA&inB&inC so the actual Request URL would be http://localhost:8080/WW_1/AAA/testget&inA&inB&inC?inA=abc&inC=def. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2019