January 2015 - 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 month, 2 weeks

2
1
0 / 0

[JBoss JIRA] (TEIID-2816) HBase Connector/Translator

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-2816?page=com.atlassian.jira.plugin... ] Kylin Soong edited comment on TEIID-2816 at 1/31/15 9:00 AM: ------------------------------------------------------------- [1] is a article show how Teiid combine HBase with HBase translator, If you want to access HBase data through JDBC, or integrate/model HBase Data using Teiid/Teiid Designer, it's a good article for you. [1] https://developer.jboss.org/wiki/TeiidOnTopOfApacheHBase > HBase Connector/Translator > -------------------------- > > Key: TEIID-2816 > URL: https://issues.jboss.org/browse/TEIID-2816 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Connector, JDBC Driver > Affects Versions: Open To Community > Reporter: devin pinkston > Assignee: Kylin Soong > Labels: HBase, Translator > Fix For: 8.10 > > > Develop a HBase translator/connector. Potentially using the Phoenix JDBC driver, supports most SQL and handles connections: > https://github.com/forcedotcom/phoenix -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3318) Support dynamically configuring the JDG protobuf schema

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3318?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3318: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1187362|https://bugzilla.redhat.com/show_bug.cgi?id=1187362] from NEW to ASSIGNED > Support dynamically configuring the JDG protobuf schema > ------------------------------------------------------- > > Key: TEIID-3318 > URL: https://issues.jboss.org/browse/TEIID-3318 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > > Need to add the ability to dynamically configure the protobuf schema. A > snip-it from an example: > // generate and register a Protobuf schema and marshallers based on Note class and the referenced classes (User class) > ProtoSchemaBuilder protoSchemaBuilder = new ProtoSchemaBuilder(); > String generatedSchema = protoSchemaBuilder > .fileName("sample_schema.proto") > .packageName("sample_package") > .addClass(Note.class) > .build(serCtx); > This would change the need for the user to implement marshallers. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3288) Upgrade JDG DSL querying using hotrod client over protobuffers to JDG 6.4

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3288?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3288: ------------------------------- Fix Version/s: 8.7.1 > Upgrade JDG DSL querying using hotrod client over protobuffers to JDG 6.4 > ------------------------------------------------------------------------- > > Key: TEIID-3288 > URL: https://issues.jboss.org/browse/TEIID-3288 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Quick Starts > Affects Versions: 8.7.1, 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7.1 > > > Upgrade the JDG DSL remote hotrod client over protobuffers from the JDG 6.3 tech preview to JDG 6.4. > This upgrade will allow user to specify what's query able using annotations and will eliminate the dependency protobuf jar. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3288) Upgrade JDG DSL querying using hotrod client over protobuffers to JDG 6.4

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3288?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3288: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/401 > Upgrade JDG DSL querying using hotrod client over protobuffers to JDG 6.4 > ------------------------------------------------------------------------- > > Key: TEIID-3288 > URL: https://issues.jboss.org/browse/TEIID-3288 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Quick Starts > Affects Versions: 8.7.1, 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7.1 > > > Upgrade the JDG DSL remote hotrod client over protobuffers from the JDG 6.3 tech preview to JDG 6.4. > This upgrade will allow user to specify what's query able using annotations and will eliminate the dependency protobuf jar. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1680) issues with correlation and aggregation

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1680?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1680. ----------------------------------- Resolution: Done Updated the validation and planner logic to allow correlated grouping expressions. > issues with correlation and aggregation > --------------------------------------- > > Key: TEIID-1680 > URL: https://issues.jboss.org/browse/TEIID-1680 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > subqueries used in the having/select clause of a query with grouping only understand correlated element symbols - not correlated grouping expressions or correlated aggregate values. > If a nested aggregate contains only outer references, then it should be treated as a correlated value. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3314) Add translator for Elasticsearch

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3314?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3314: ------------------------------------- Fix Version/s: Open To Community Assignee: (was: Steven Hawkins) > Add translator for Elasticsearch > -------------------------------- > > Key: TEIID-3314 > URL: https://issues.jboss.org/browse/TEIID-3314 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Tom Arnold > Labels: spatial > Fix For: Open To Community > > > Elasticseach is an open source search server based on Lucene. > Use case would be similar to that of SOLR. There is a (slightly outdated) comparsion between the two here: http://solr-vs-elasticsearch.com/. > Java API docs are here: http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/curre... > Filter DSL documentation is here: http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/curre... > JBoss EAP 6 module docs: http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/curre... > It supports several types of spatial filters: > * Bounding box > * Polygon > * Shape - This is based on JTS; I think the difference between this and Polygon is this allows options like WITHIN/INTERSECTS/DISJOINT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2469) Pre-Load Materialised Views

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2469?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2469: ---------------------------------- Summary: Pre-Load Materialised Views (was: Load Materialised Views) Fix Version/s: 8.11 Component/s: Server Putting into the 8.11 bucket to further align the internal/external materialization logic so that the can be an option to pre-load internal materialized views. > Pre-Load Materialised Views > --------------------------- > > Key: TEIID-2469 > URL: https://issues.jboss.org/browse/TEIID-2469 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.1 > Reporter: Gautam Banerjee > Assignee: Steven Hawkins > Fix For: 8.11 > > > Currently teiid does not load materialised views automatically. The request has to come for the materialised view or it has to be explicitly loaded. As materialised views are made with the purpose of preloading data, teiid should load the materialised views as default. There can be a tag or switch which will determine if the materialise views are to be preloaded or not. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3288) Upgrade JDG DSL querying using hotrod client over protobuffers to JDG 6.4

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3288?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3288: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1183046|https://bugzilla.redhat.com/show_bug.cgi?id=1183046] from ASSIGNED to MODIFIED > Upgrade JDG DSL querying using hotrod client over protobuffers to JDG 6.4 > ------------------------------------------------------------------------- > > Key: TEIID-3288 > URL: https://issues.jboss.org/browse/TEIID-3288 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Quick Starts > Affects Versions: 8.7.1, 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > > Upgrade the JDG DSL remote hotrod client over protobuffers from the JDG 6.3 tech preview to JDG 6.4. > This upgrade will allow user to specify what's query able using annotations and will eliminate the dependency protobuf jar. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3300) Add SPATIAL_REF_SYS table

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3300?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3300: ---------------------------------- Component/s: Query Engine > Add SPATIAL_REF_SYS table > ------------------------- > > Key: TEIID-3300 > URL: https://issues.jboss.org/browse/TEIID-3300 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > Fix For: 8.10 > > > Implement SPATIAL_REF_SYS table (from the OGC Simple Features spec). This table stores metadata about different coordinate systems and how to tranform between them. See [here|http://en.wikipedia.org/wiki/SRID] and [here|http://www.carocoops.org/resources/doc/postgis/x321.html] for details. > {code} > CREATE TABLE SPATIAL_REF_SYS > ( > SRID INTEGER NOT NULL PRIMARY KEY, > AUTH_NAME CHARACTER VARYING(256), > AUTH_SRID INTEGER, > SRTEXT CHARACTER VARYING(2048) > ) > {code} > https://raw.githubusercontent.com/postgis/postgis/svn-trunk/spatial_ref_s... > This would be used in conjunction with the GeoTools referencing module or Proj4J to transform between coordinate systems in Teiid (ST_Transform function). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 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 2015