November 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5535) CTE: Inconsistent Error Message when SELECTing a View Instead of its Definition

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5535?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5535: --------------------------------------- [~dalex005] Thanks for checking so promptly. I need to see if there is a safer way to do that projection minimization such that a better error will occur if planning goes wrong. > CTE: Inconsistent Error Message when SELECTing a View Instead of its Definition > ------------------------------------------------------------------------------- > > Key: TEIID-5535 > URL: https://issues.jboss.org/browse/TEIID-5535 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.1 > Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Critical > > There are queries involving CTEs and set operators that can be executed and return results. > However, creating a view based on the working queries makes these views unusable as they return an error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5529) Non-pushed subquery may have evaluatable predicates not pushed

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5529?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5529. ----------------------------------- Resolution: Done Updated the criteria validation logic to selectively use different checks of whether an expression will evaluate to a constant depending upon whether it's in the context of just a query or the inclusion of a subquery for pushdown. > Non-pushed subquery may have evaluatable predicates not pushed > -------------------------------------------------------------- > > Key: TEIID-5529 > URL: https://issues.jboss.org/browse/TEIID-5529 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > For example, a source that does not support lower nor correlated subqueries and a query like: > SELECT array_agg((select intkey from bqt1.smallb where stringkey = lower(a.stringkey))) from bqt1.smalla a > will not push stringkey = lower(a.stringkey) to the n-many subquery, even though it can be pre-evaluated with the correlated value. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5531) Implicit indexing of common tables doesn't consider composite keys

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5531?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5531. ----------------------------------- Fix Version/s: 11.2.1 Resolution: Done Updated the logic to look across all predicates with matching operators. This is still a naive approach - it does not actually check ndv counts or other stats to see what columns would make for the best index. However the performance is much improved in situations where the first predicate is against something that is not sufficiently unique. > Implicit indexing of common tables doesn't consider composite keys > ------------------------------------------------------------------ > > Key: TEIID-5531 > URL: https://issues.jboss.org/browse/TEIID-5531 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > Using a common table that is referenced by a common predicate will create an implicit index, but only for the first attribute - in the case of a composite key a multi-column index will only be created if an array/row value comparison is used. > For example: > with (x) as (...) > select (... from x where x.col1 = y.col1 and x.col2 = y.col2) ... from y > should add an index on x using both col1 and col2. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5537) Move Thorntail examples to use new modules

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5537?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5537: --------------------------------------- I'm fine if we put everything under a single repo. > Move Thorntail examples to use new modules > ------------------------------------------ > > Key: TEIID-5537 > URL: https://issues.jboss.org/browse/TEIID-5537 > Project: Teiid > Issue Type: Sub-task > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > Also, how about closing the "thorntail-examples" repo and merging the examples with the new Thontail repo? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5537) Move Thorntail examples to use new modules

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5537?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5537: ------------------------------------- yeah, that is what I started out with https://github.com/rareddy/teiid-thorntail > Move Thorntail examples to use new modules > ------------------------------------------ > > Key: TEIID-5537 > URL: https://issues.jboss.org/browse/TEIID-5537 > Project: Teiid > Issue Type: Sub-task > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > Also, how about closing the "thorntail-examples" repo and merging the examples with the new Thontail repo? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5535) CTE: Inconsistent Error Message when SELECTing a View Instead of its Definition

by dalex dalex (Jira)

[ https://issues.jboss.org/browse/TEIID-5535?page=com.atlassian.jira.plugin... ] dalex dalex commented on TEIID-5535: ------------------------------------ [~shawkins] thx a lot! I've just checked the TEIID-5532 issue and it solved my problem. > CTE: Inconsistent Error Message when SELECTing a View Instead of its Definition > ------------------------------------------------------------------------------- > > Key: TEIID-5535 > URL: https://issues.jboss.org/browse/TEIID-5535 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.1 > Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Critical > > There are queries involving CTEs and set operators that can be executed and return results. > However, creating a view based on the working queries makes these views unusable as they return an error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5537) Move Thorntail examples to use new modules

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5537?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-5537 at 11/9/18 11:29 AM: ----------------------------------------------------------------- The top level would be the teiid organization. There would be a new repo called thorntail, which would have the three directories underneath. I suppose it would be better to call it the teiid-thorntail repo. was (Author: shawkins): The top level would be the teiid organization. There would be a new repo called thorntail, which would have the three directories underneath. > Move Thorntail examples to use new modules > ------------------------------------------ > > Key: TEIID-5537 > URL: https://issues.jboss.org/browse/TEIID-5537 > Project: Teiid > Issue Type: Sub-task > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > Also, how about closing the "thorntail-examples" repo and merging the examples with the new Thontail repo? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5537) Move Thorntail examples to use new modules

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5537?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5537: --------------------------------------- The top level would be the teiid organization. There would be a new repo called thorntail, which would have the three directories underneath. > Move Thorntail examples to use new modules > ------------------------------------------ > > Key: TEIID-5537 > URL: https://issues.jboss.org/browse/TEIID-5537 > Project: Teiid > Issue Type: Sub-task > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > Also, how about closing the "thorntail-examples" repo and merging the examples with the new Thontail repo? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5537) Move Thorntail examples to use new modules

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5537?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-5537 at 11/9/18 11:08 AM: --------------------------------------------------------------- Not in mainline Teiid repo, but yes in a teiid-thorntail repo like above. But I did not consider the main teiid repo before, but that is not a bad idea either to be under one roof. was (Author: rareddy): Not in mainline Teiid repo, but yes in a teiid-thorntail repo like above. > Move Thorntail examples to use new modules > ------------------------------------------ > > Key: TEIID-5537 > URL: https://issues.jboss.org/browse/TEIID-5537 > Project: Teiid > Issue Type: Sub-task > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > Also, how about closing the "thorntail-examples" repo and merging the examples with the new Thontail repo? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5537) Move Thorntail examples to use new modules

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5537?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5537: ------------------------------------- Not in mainline Teiid repo, but yes in a teiid-thorntail repo like above. > Move Thorntail examples to use new modules > ------------------------------------------ > > Key: TEIID-5537 > URL: https://issues.jboss.org/browse/TEIID-5537 > Project: Teiid > Issue Type: Sub-task > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > Also, how about closing the "thorntail-examples" repo and merging the examples with the new Thontail repo? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2018