August 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4395) Oracle translator should pushdown clob conversion

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4395?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4395. ----------------------------------- Resolution: Done Used the DBMS_LOB.substr so that we can have the same truncate behavior on large clobs. > Oracle translator should pushdown clob conversion > ------------------------------------------------- > > Key: TEIID-4395 > URL: https://issues.jboss.org/browse/TEIID-4395 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Affects Versions: 9.0.2 > Reporter: Tom Arnold > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.3 > > > We have an "attributes" table defined like this > {code:sql} > CREATE TABLE "ATTRS" > ( > NAME varchar2(50) NOT NULL, > ATTR_NAME varchar2(50) NOT NULL, > ATTR_VALUE clob, > CONSTRAINT ATTRS_PK PRIMARY KEY (NAME,ATTR_NAME) > ); > {code} > The value column is unfortunately defined as a clob, but most of the data is small enough to fit in varchar (4000 chars). We have a somewhat complex query that ends up grouping by the clob value and with Teiid it is causing N-many queries. > Simplified to this > {code:sql} > select cast(attr_value as varchar) from attrs > {code} > {code} > ProjectNode > + Relational Node ID:0 > + Output Columns:expr1 (string) > + Statistics: > 0: Node Output Rows: 293 > 1: Node Next Batch Process Time: 5 > 2: Node Cumulative Next Batch Process Time: 5 > 3: Node Cumulative Process Time: 11 > 4: Node Next Batch Calls: 2 > 5: Node Blocks: 1 > + Cost Estimates:Estimated Node Cardinality: 293.0 > + Child 0: > AccessNode > + Relational Node ID:1 > + Output Columns:ATTR_VALUE (clob) > + Statistics: > 0: Node Output Rows: 293 > 1: Node Next Batch Process Time: 0 > 2: Node Cumulative Next Batch Process Time: 0 > 3: Node Cumulative Process Time: 6 > 4: Node Next Batch Calls: 2 > 5: Node Blocks: 1 > + Cost Estimates:Estimated Node Cardinality: 293.0 > + Query:SELECT g_0.ATTR_VALUE FROM foo.ATTRS AS g_0 > + Model Name:foo > + Select Columns:convert(foo.ATTRS.ATTR_VALUE, varchar) > + Data Bytes Sent:6783 > + Planning Time:2 > {code} > Ideally on Oracle it would just get pushed down like this > {code:sql} > SELECT TO_CHAR(g_0.ATTR_VALUE) FROM foo.ATTRS AS g_0 > {code} > From looking in the Oracle translator it looks like it should do this already... I added a test case which passes, but the plan seems to disagree. > {code:java} > @Test public void testClobToString() throws Exception { > Column column = new Column(); > column.setNativeType("CLOB"); > column.setNameInSource("dt"); > helpTest(LANG_FACTORY.createColumnReference("dt", LANG_FACTORY.createNamedTable("x", null, null), column, Clob.class), "varchar", "to_char(x.dt)"); //$NON-NLS-1$ //$NON-NLS-2$ > } > {code} > As a workaround I added a CLOB_TO_CHAR foreign function in the model DDL (using teiid_rel:native-query 'TO_CHAR($1)') and changed my query to use that instead of cast, but I'd prefer to not have to do that in the long term. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4357) Add documentation on exposing Teiid as a GeoServer data source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4357?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4357: ---------------------------------- Summary: Add documentation on exposing Teiid as a GeoServer data source (was: Add documentation on exposing Teiid as a GeoServer data souce) > Add documentation on exposing Teiid as a GeoServer data source > -------------------------------------------------------------- > > Key: TEIID-4357 > URL: https://issues.jboss.org/browse/TEIID-4357 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.1 > > > Based on the details in TEIID-3869, need to document how Teiid can be exposed as a GeoServer data source -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4395) Oracle translator should pushdown clob conversion

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4395?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4395: ---------------------------------- Issue Type: Enhancement (was: Bug) Fix Version/s: 9.1 9.0.3 By default we don't push the conversion to and from lobs as they typically involve special handling. It is something that we do need to expand on though. > Oracle translator should pushdown clob conversion > ------------------------------------------------- > > Key: TEIID-4395 > URL: https://issues.jboss.org/browse/TEIID-4395 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Affects Versions: 9.0.2 > Reporter: Tom Arnold > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.3 > > > We have an "attributes" table defined like this > {code:sql} > CREATE TABLE "ATTRS" > ( > NAME varchar2(50) NOT NULL, > ATTR_NAME varchar2(50) NOT NULL, > ATTR_VALUE clob, > CONSTRAINT ATTRS_PK PRIMARY KEY (NAME,ATTR_NAME) > ); > {code} > The value column is unfortunately defined as a clob, but most of the data is small enough to fit in varchar (4000 chars). We have a somewhat complex query that ends up grouping by the clob value and with Teiid it is causing N-many queries. > Simplified to this > {code:sql} > select cast(attr_value as varchar) from attrs > {code} > {code} > ProjectNode > + Relational Node ID:0 > + Output Columns:expr1 (string) > + Statistics: > 0: Node Output Rows: 293 > 1: Node Next Batch Process Time: 5 > 2: Node Cumulative Next Batch Process Time: 5 > 3: Node Cumulative Process Time: 11 > 4: Node Next Batch Calls: 2 > 5: Node Blocks: 1 > + Cost Estimates:Estimated Node Cardinality: 293.0 > + Child 0: > AccessNode > + Relational Node ID:1 > + Output Columns:ATTR_VALUE (clob) > + Statistics: > 0: Node Output Rows: 293 > 1: Node Next Batch Process Time: 0 > 2: Node Cumulative Next Batch Process Time: 0 > 3: Node Cumulative Process Time: 6 > 4: Node Next Batch Calls: 2 > 5: Node Blocks: 1 > + Cost Estimates:Estimated Node Cardinality: 293.0 > + Query:SELECT g_0.ATTR_VALUE FROM foo.ATTRS AS g_0 > + Model Name:foo > + Select Columns:convert(foo.ATTRS.ATTR_VALUE, varchar) > + Data Bytes Sent:6783 > + Planning Time:2 > {code} > Ideally on Oracle it would just get pushed down like this > {code:sql} > SELECT TO_CHAR(g_0.ATTR_VALUE) FROM foo.ATTRS AS g_0 > {code} > From looking in the Oracle translator it looks like it should do this already... I added a test case which passes, but the plan seems to disagree. > {code:java} > @Test public void testClobToString() throws Exception { > Column column = new Column(); > column.setNativeType("CLOB"); > column.setNameInSource("dt"); > helpTest(LANG_FACTORY.createColumnReference("dt", LANG_FACTORY.createNamedTable("x", null, null), column, Clob.class), "varchar", "to_char(x.dt)"); //$NON-NLS-1$ //$NON-NLS-2$ > } > {code} > As a workaround I added a CLOB_TO_CHAR foreign function in the model DDL (using teiid_rel:native-query 'TO_CHAR($1)') and changed my query to use that instead of cast, but I'd prefer to not have to do that in the long term. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4394) Impala Translator - add pushdown support for window functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4394?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4394. ----------------------------------- Fix Version/s: 9.1 Resolution: Done Committed the pull request. Will be in place for Beta1. > Impala Translator - add pushdown support for window functions > ------------------------------------------------------------- > > Key: TEIID-4394 > URL: https://issues.jboss.org/browse/TEIID-4394 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.0.2 > Reporter: Don Krapohl > Assignee: Steven Hawkins > Labels: Impala_Translator > Fix For: 9.1 > > > Cloudera Impala supports window functions per http://www.cloudera.com/documentation/archive/impala/2-x/2-1-x/topics/imp... > As a query executor I need to be able to push down window functions into Impala. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4357) Add documentation on exposing Teiid as a GeoServer data souce

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4357?page=com.atlassian.jira.plugin... ] Work on TEIID-4357 started by Steven Hawkins. --------------------------------------------- > Add documentation on exposing Teiid as a GeoServer data souce > ------------------------------------------------------------- > > Key: TEIID-4357 > URL: https://issues.jboss.org/browse/TEIID-4357 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.1 > > > Based on the details in TEIID-3869, need to document how Teiid can be exposed as a GeoServer data source -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4390) Expand level support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4390?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4390. ----------------------------------- Resolution: Done Added levels support in both the * and the self relationship case. > Expand level support > -------------------- > > Key: TEIID-4390 > URL: https://issues.jboss.org/browse/TEIID-4390 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > We should support the level construct for expand to support recursive relationships. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4399) Remove $levels restrictions

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4399: ------------------------------------- Summary: Remove $levels restrictions Key: TEIID-4399 URL: https://issues.jboss.org/browse/TEIID-4399 Project: Teiid Issue Type: Sub-task Components: OData Reporter: Steven Hawkins Assignee: Ramesh Reddy Once https://issues.apache.org/jira/browse/OLINGO-1009 is addressed the ODataSQLBuilder restrictions for OLINGO-1009 in the processExpandOption should be removed. Also additional unit tests will be needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4390) Expand level support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4390?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4390: --------------------------------------- https://issues.apache.org/jira/browse/OLINGO-1009 prevents us from fully supporting this. > Expand level support > -------------------- > > Key: TEIID-4390 > URL: https://issues.jboss.org/browse/TEIID-4390 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > We should support the level construct for expand to support recursive relationships. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4320) Costing calculation issues

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4320?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-4320. -------------------------------- Resolution: Done > Costing calculation issues > -------------------------- > > Key: TEIID-4320 > URL: https://issues.jboss.org/browse/TEIID-4320 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.1, 8.7.8.6_2, 8.12.6.6_3, 9.0.1, 8.13.6 > > > When determining if a dependent join should be used we'll rule out too many scenarios based upon requiring additional ndv info - when that can be determined from cardinality alone. Also we are inappropriately assuming key usage in predicate costing - as it does not consider the node which may not represent a single table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4320) Costing calculation issues

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4320?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4320: --------------------------------- Fix Version/s: 8.12.6.6_3 > Costing calculation issues > -------------------------- > > Key: TEIID-4320 > URL: https://issues.jboss.org/browse/TEIID-4320 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.1, 8.13.6, 9.0.1, 8.7.8.6_2, 8.12.6.6_3 > > > When determining if a dependent join should be used we'll rule out too many scenarios based upon requiring additional ndv info - when that can be determined from cardinality alone. Also we are inappropriately assuming key usage in predicate costing - as it does not consider the node which may not represent a single table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2016