[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
2 months
[JBoss JIRA] (TEIID-4315) HBase Quickstart issues
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4315?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4315:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1335006, https://bugzilla.redhat.com/show_bug.cgi?id=1335004, https://bugzilla.redhat.com/show_bug.cgi?id=1335002 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1335006, https://bugzilla.redhat.com/show_bug.cgi?id=1335004)
> HBase Quickstart issues
> -----------------------
>
> Key: TEIID-4315
> URL: https://issues.jboss.org/browse/TEIID-4315
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
>
> remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:
> From:
> > module remove --name=org.apache.phoenix
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > module remove --name=org.apache.phoenix
> -------
> As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:
> From:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> > /subsystem=datasources/data-source=QSPhoenixDS:enable
> ------
> Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli
> Line: 57 - 3) Setup Phoenix Data Source
> 1 - --resources=phoenix-4.2.1-client.jar
> Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (TEIID-4315) HBase Quickstart issues
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4315?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4315:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1335006
Bugzilla Update: Perform
> HBase Quickstart issues
> -----------------------
>
> Key: TEIID-4315
> URL: https://issues.jboss.org/browse/TEIID-4315
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
>
> remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:
> From:
> > module remove --name=org.apache.phoenix
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > module remove --name=org.apache.phoenix
> -------
> As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:
> From:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> > /subsystem=datasources/data-source=QSPhoenixDS:enable
> ------
> Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli
> Line: 57 - 3) Setup Phoenix Data Source
> 1 - --resources=phoenix-4.2.1-client.jar
> Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (TEIID-4315) HBase Quickstart issues
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4315?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4315:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1335006, https://bugzilla.redhat.com/show_bug.cgi?id=1335004 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1335006)
> HBase Quickstart issues
> -----------------------
>
> Key: TEIID-4315
> URL: https://issues.jboss.org/browse/TEIID-4315
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
>
> remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:
> From:
> > module remove --name=org.apache.phoenix
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:remove()
> > /subsystem=datasources/jdbc-driver=phoenix:remove()
> > module remove --name=org.apache.phoenix
> -------
> As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:
> From:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)
> To:
> > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> > /subsystem=datasources/data-source=QSPhoenixDS:enable
> ------
> Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli
> Line: 57 - 3) Setup Phoenix Data Source
> 1 - --resources=phoenix-4.2.1-client.jar
> Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (TEIID-4315) HBase Quickstart issues
by Van Halbert (JIRA)
Van Halbert created TEIID-4315:
----------------------------------
Summary: HBase Quickstart issues
Key: TEIID-4315
URL: https://issues.jboss.org/browse/TEIID-4315
Project: Teiid
Issue Type: Bug
Components: Quick Starts
Affects Versions: 9.x
Reporter: Van Halbert
Assignee: Van Halbert
Priority: Minor
remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:
From:
> module remove --name=org.apache.phoenix
> /subsystem=datasources/jdbc-driver=phoenix:remove()
> /subsystem=datasources/data-source=QSPhoenixDS:remove()
To:
> /subsystem=datasources/data-source=QSPhoenixDS:remove()
> /subsystem=datasources/jdbc-driver=phoenix:remove()
> module remove --name=org.apache.phoenix
-------
As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:
From:
> /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)
To:
> /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> /subsystem=datasources/data-source=QSPhoenixDS:enable
------
Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli
Line: 57 - 3) Setup Phoenix Data Source
1 - --resources=phoenix-4.2.1-client.jar
Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (TEIID-3351) Quick Start "dynamicvdb-datafederation" needlessly made complicated
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3351?page=com.atlassian.jira.plugin... ]
Van Halbert resolved TEIID-3351.
--------------------------------
Fix Version/s: 9.x
(was: 8.12.x)
Resolution: Done
> Quick Start "dynamicvdb-datafederation" needlessly made complicated
> -------------------------------------------------------------------
>
> Key: TEIID-3351
> URL: https://issues.jboss.org/browse/TEIID-3351
> Project: Teiid
> Issue Type: Quality Risk
> Components: Quick Starts
> Reporter: Ramesh Reddy
> Assignee: Van Halbert
> Fix For: 9.x
>
>
> The "dynamicvdb-datafederation" example in the Quick Starts example is needlessly made complicated. Originally this is designed to have one File and RDBMS source, to show a simple data integration through Teiid.
> Now, it has
> - Excel integration
> - Materialization Example
> - more models
> I am not opposed to having these features shown in an example, however not in this example. This needs to be as simple as possible to show a quick introduction to the Teiid. Please move these into separate quick starts.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months