August 2016 - teiid-issues - Jboss List Archives

[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 reopened TEIID-4320: ---------------------------------- > 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 > > > 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-4304) Correct handling with subquery in on clause

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4304?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-4304. -------------------------------- Resolution: Done > Correct handling with subquery in on clause > ------------------------------------------- > > Key: TEIID-4304 > URL: https://issues.jboss.org/browse/TEIID-4304 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2, 8.12.6.6_3, 9.0.2, 9.0.1 > > > With the translator capability supportsSubqueryInOn false, we can still plan a query with a subquery in the on clause if non-join criteria on the inner side of a left outer join is used in the user query on clause (it is temporarily pushed out of the join and then added back in rule collapse source). > Additionally the oracle translator should not support subquery in on for oracle 11 and earlier. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4304) Correct handling with subquery in on clause

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4304?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4304: --------------------------------- Fix Version/s: 8.12.6.6_3 > Correct handling with subquery in on clause > ------------------------------------------- > > Key: TEIID-4304 > URL: https://issues.jboss.org/browse/TEIID-4304 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.1, 8.7.8.6_2, 9.0.2, 8.12.6.6_3 > > > With the translator capability supportsSubqueryInOn false, we can still plan a query with a subquery in the on clause if non-join criteria on the inner side of a left outer join is used in the user query on clause (it is temporarily pushed out of the join and then added back in rule collapse source). > Additionally the oracle translator should not support subquery in on for oracle 11 and earlier. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4304) Correct handling with subquery in on clause

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4304?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-4304: ---------------------------------- > Correct handling with subquery in on clause > ------------------------------------------- > > Key: TEIID-4304 > URL: https://issues.jboss.org/browse/TEIID-4304 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.1, 8.7.8.6_2, 9.0.2 > > > With the translator capability supportsSubqueryInOn false, we can still plan a query with a subquery in the on clause if non-join criteria on the inner side of a left outer join is used in the user query on clause (it is temporarily pushed out of the join and then added back in rule collapse source). > Additionally the oracle translator should not support subquery in on for oracle 11 and earlier. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4278) MySQL 5 should support distinct aggregates

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4278?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-4278. -------------------------------- Resolution: Done > MySQL 5 should support distinct aggregates > ------------------------------------------ > > Key: TEIID-4278 > URL: https://issues.jboss.org/browse/TEIID-4278 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2, 8.12.6.6_3 > > > Older versions of mysql only supported distinct count, but later versions supported distinct with all relevant aggregates. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4278) MySQL 5 should support distinct aggregates

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4278?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4278: --------------------------------- Fix Version/s: 8.12.6.6_3 > MySQL 5 should support distinct aggregates > ------------------------------------------ > > Key: TEIID-4278 > URL: https://issues.jboss.org/browse/TEIID-4278 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2, 8.12.6.6_3 > > > Older versions of mysql only supported distinct count, but later versions supported distinct with all relevant aggregates. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4278) MySQL 5 should support distinct aggregates

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4278?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-4278: ---------------------------------- > MySQL 5 should support distinct aggregates > ------------------------------------------ > > Key: TEIID-4278 > URL: https://issues.jboss.org/browse/TEIID-4278 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2 > > > Older versions of mysql only supported distinct count, but later versions supported distinct with all relevant aggregates. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4323) Add support for first/last/absolute/relative "FETCH " syntax

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4323?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-4323. -------------------------------- Resolution: Done > Add support for first/last/absolute/relative "FETCH " syntax > ------------------------------------------------------------ > > Key: TEIID-4323 > URL: https://issues.jboss.org/browse/TEIID-4323 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2, 8.12.6.6_3 > > > Add Support for the below FETCH syntax: > FETCH LAST FROM cursor_name > FETCH ABSOLUTE fetch_when FROM cursor_name > FETCH RELATIVE fetch_when FROM cursor_name > FETCH FIRST FROM cursor_name -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4323) Add support for first/last/absolute/relative "FETCH " syntax

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4323?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4323: --------------------------------- Fix Version/s: 8.12.6.6_3 > Add support for first/last/absolute/relative "FETCH " syntax > ------------------------------------------------------------ > > Key: TEIID-4323 > URL: https://issues.jboss.org/browse/TEIID-4323 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2, 8.12.6.6_3 > > > Add Support for the below FETCH syntax: > FETCH LAST FROM cursor_name > FETCH ABSOLUTE fetch_when FROM cursor_name > FETCH RELATIVE fetch_when FROM cursor_name > FETCH FIRST FROM cursor_name -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4289) Add transaction command support for syntax BEGIN/ROLLBACK/COMMIT WORK

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4289?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-4289: ---------------------------------- > Add transaction command support for syntax BEGIN/ROLLBACK/COMMIT WORK > --------------------------------------------------------------------- > > Key: TEIID-4289 > URL: https://issues.jboss.org/browse/TEIID-4289 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.7.6.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2 > > > This request appears to be an expansion of TEIID-1701 to add syntax like the below as an alias for transactional commands. This would be in line to make commands portable from other vendor DBs such as PostgreSQL/SQL Server/DB2/MySQL. > BEGIN WORK > ROLLBACK WORK > COMMIT WORK -- 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