May 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-160) Remove redundant self-joins

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-160?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-160. ---------------------------------- Resolution: Deferred > Remove redundant self-joins > --------------------------- > > Key: TEIID-160 > URL: https://issues.jboss.org/browse/TEIID-160 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > Query minimization should be used to remove self-joins on unique columns. This could be added as part of RuleRemoveOptionalJoins (but the rule may need to be run again after join planning). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1268) Add support for using the case insensitive metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1268?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1268. ----------------------------------- Resolution: Deferred > Add support for using the case insensitive metadata > --------------------------------------------------- > > Key: TEIID-1268 > URL: https://issues.jboss.org/browse/TEIID-1268 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > > We currently capture whether the source is case sensitive and thus have a place holder on both physical and virtual models, but we do not use this information in performing comparisons in teiid. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4810) Translator Caching

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4810?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4810: ---------------------------------- Fix Version/s: 11.0 Will access for 11.0 if there is a simple built-in set of options that we want to have on all translators for enabling caching, rather than requiring a custom translator (this could also be handled with a delegating/proxy translator). > Translator Caching > ------------------ > > Key: TEIID-4810 > URL: https://issues.jboss.org/browse/TEIID-4810 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors, Query Engine > Affects Versions: 9.3 > Reporter: Van Halbert > Fix For: 11.0 > > > we also have a whole different level of caching for custom translators > we could expand on that > we could cache on any source query > that’s not something we’ve talked about putting any higher level UI around > this would be a development and documentation effort > this is different than the whole model materialisation > the difference is that this is at a source query level > vs when you are using cache hints and extension metadata > we don’t have anything for the design-time user > that’s another feature set around caching that we could put some exposure on it > otherwise it’s not really exposed > the idea there is that if you want to do some higher level caching > you can build that into your models or your user query > we could turn it on and off without having to use a custom translator > MMX had a feature like that but it was convoluted because it was mixed up with the user level query caching and they had to be enabled together > Attachments -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4537) Store ddl as fully qualified

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4537?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4537. ----------------------------------- Resolution: Out of Date The implementation was changed to no longer be interactive in the first cut, so there isn't a need for the storage option yet. > Store ddl as fully qualified > ---------------------------- > > Key: TEIID-4537 > URL: https://issues.jboss.org/browse/TEIID-4537 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > > To prevent later statements (in particular create) from causing issues with existing objects, the original sql will need to be stored fully qualified. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3637) Query Plan/Execution Plan Enhancements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3637?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3637. ----------------------------------- Resolution: Incomplete Description > Query Plan/Execution Plan Enhancements > -------------------------------------- > > Key: TEIID-3637 > URL: https://issues.jboss.org/browse/TEIID-3637 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.7.1 > Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > Priority: Critical > > Query Plan / Execution plan, for any particular query is lacking more explicit information about what the query engine is doing for each query. Would like to know if its JDV doing the processing vs doing push down optimization, and what is the path it takes if its internal to JDV, and also the costs associated with every step. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5306) JDG is doing away with hot rod client, going primarily with rest interface

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5306?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5306: ------------------------------------- Issue Type: Quality Risk (was: Feature Request) Fix Version/s: 11.0 Assignee: Van Halbert (was: Steven Hawkins) > JDG is doing away with hot rod client, going primarily with rest interface > -------------------------------------------------------------------------- > > Key: TEIID-5306 > URL: https://issues.jboss.org/browse/TEIID-5306 > Project: Teiid > Issue Type: Quality Risk > Components: JDG Connector > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Fix For: 11.0 > > > JDG is deprecating the JDG 7.2.x hot rod client and moving to provide exclusively rest interfaces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5257) Sysadmin Usage table doesn't track column-level usage by a virtual procedure

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5257?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5257: ---------------------------------- Fix Version/s: 11.0 > Sysadmin Usage table doesn't track column-level usage by a virtual procedure > ---------------------------------------------------------------------------- > > Key: TEIID-5257 > URL: https://issues.jboss.org/browse/TEIID-5257 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.12.11.6_4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 11.0 > > > There are not column-level dependencies in relation 'Virtual procedure column -> View/table column'. > For this vdb: > {code:xml|title=vdb} > <model name="insideVirtualModel" type="VIRTUAL"> > <metadata type="DDL"> > <![CDATA[ > CREATE VIEW v1 (v1col string) AS SELECT 'a' UNION ALL SELECT 'b'; > CREATE VIEW v2 (v2col string) AS SELECT v1col||'b' FROM v1; > CREATE VIRTUAL PROCEDURE p1() RETURNS (p1col string) AS > BEGIN > SELECT v2col FROM v2; > END > CREATE VIEW v7 (v7col string) AS SELECT p1.p1col FROM (CALL p1())AS p1; > ]]> > </metadata> > </model> > <model name="dependentOnPhysicalModel" type="VIRTUAL"> > <metadata type="DDL"> > <![CDATA[ > CREATE VIEW v3 (v3col string) AS SELECT t1col||'b' FROM t1; > CREATE VIEW v4 (v4col string) AS SELECT p.p2col FROM (CALL p2(1)) AS p; > ]]> > </metadata> > </model> > {code} > Following query: > {code:sql|title=SYSADMIN.Usage query} > SELECT * FROM SYSADMIN.Usage WHERE VDBName='vdbname' AND SchemaName='insideVirtualModel' AND Name='p1' AND object_type='Column' AND Uses_object_type='Column' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5135) REPEAT function truncates strings to 4000 characters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5135?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5135: ---------------------------------- Fix Version/s: 11.0 > REPEAT function truncates strings to 4000 characters > ---------------------------------------------------- > > Key: TEIID-5135 > URL: https://issues.jboss.org/browse/TEIID-5135 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 9.3.4 > Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Minor > Fix For: 11.0 > > > Probably it's not bug. When running the following queries: > {code:sql} > Select Length(Repeat('abcde', 9000));; /* 4000 chars */ > Select Length(Repeat('a', 9000));; /* 4000 chars */ > {code} > Teiid returns 4000 instead of 9000. Can the internal truncation be avoided (maybe in some cases) or not? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5112) Add parsing restrictions for 0 length

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5112?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5112. ----------------------------------- Fix Version/s: 10.1 Resolution: Done > Add parsing restrictions for 0 length > ------------------------------------- > > Key: TEIID-5112 > URL: https://issues.jboss.org/browse/TEIID-5112 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.1 > > > Related to TEIID-5111 the parser and other logic should ensure that length of 0 is not allowed in ddl as a length value. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2169) Buffer Manger's memory should be backed by Infinispan Cache

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2169?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2169. ----------------------------------- Resolution: Out of Date > Buffer Manger's memory should be backed by Infinispan Cache > ----------------------------------------------------------- > > Key: TEIID-2169 > URL: https://issues.jboss.org/browse/TEIID-2169 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > > Currently the buffer manager uses the memory from the local VM's heap for processing the intermediate query results, anything that overruns is saved on the disk. Using this model so far proven very efficient. > However, when it comes to using the data grid as unlimited temp backing store where the results can be shared with other nodes in the case of fail-over of the session, this in current model does not work. By using the infinispan's local cache in standalone and replicated cache in distributed node for the buffer manager these issues can resolved. > Issues may be, currently Buffer Manager uses efficient btree based index store, also the uses file storage in block. To make it work, Teiid needs to have access to the Infinispan's eviction queue and may also needs to implement the cache store. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 May 2018