August 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2568) Order by is omitted when projection is raised above ordering with grouping

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2568?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2568: --------------------------------- Fix Version/s: 7.7.8 > Order by is omitted when projection is raised above ordering with grouping > -------------------------------------------------------------------------- > > Key: TEIID-2568 > URL: https://issues.jboss.org/browse/TEIID-2568 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Environment: Windows and teiid 8.1 > Reporter: RAKESH BALGURI > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5, 7.7.8 > > Attachments: Query_Plan_SQL_1.txt, Query_Plan_SQL_2.txt > > > I have a SQL which contain constants in the Select clause and also it contains Group By, Order By and Limit clauses in the SQL. > When I execute the SQL, the Order By clause is not being pushed to the underlying translator. My translator doesn't support "SelectExpressions" i.e. supportsSelectExpression() returns false. > When I remove the constant from the Select clause then the Order By is pushed to the translator. > > Is this a bug in Teiid's query Optimizer? > > The following are the sample queries and attached are the Query Plans for both the SQL's. > > Query1: This SQL doesn't push the Order By clause to the translator. > > SELECT B.RESCLASS, COUNT(*) AS GROUPING_COUNT, 'SECURITY.BASERULE' AS "__objecttype__" FROM > SECURITY.BASERULE AS B GROUP BY B.RESCLASS ORDER BY B.RESCLASS DESC LIMIT 22 > > Query2: This SQL pushes the Order By to the translator. > > SELECT B.RESCLASS, COUNT(*) AS GROUPING_COUNT FROM > SECURITY.BASERULE AS B GROUP BY B.RESCLASS ORDER BY B.RESCLASS DESC LIMIT 22 -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2501) window functions in view return incorrect results

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2501?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2501: --------------------------------- Fix Version/s: 7.7.8 > window functions in view return incorrect results > ------------------------------------------------- > > Key: TEIID-2501 > URL: https://issues.jboss.org/browse/TEIID-2501 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.4, 7.7.8 > > > conditions and limits above a view are too broadly allowed to be pushed through a view layer containing window functions. > From the forum posting for example: > {code} > SELECT > "StateProvinceID" > , COUNT(*) OVER (PARTITION BY a."CountryRegionCode") AS num > FROM salestaxrate a > WHERE "TaxType" = 3{code} > returns the correct counts, where as > {code} > SELECT * > FROM > ( > SELECT > "StateProvinceID" > , COUNT(*) OVER (PARTITION BY a."CountryRegionCode") AS num > FROM salestaxrate a > WHERE "TaxType" = 3 > ) x > WHERE "StateProvinceID" = 45 > {code} > returns counts where the state province id condition is applied before the windowing. > The currently logic will only prevent the criteria from being pushed if it is directly applied against a computed window value. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2500) Rewrite of case with true condition is not correct

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2500?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2500: --------------------------------- Fix Version/s: 7.7.8 > Rewrite of case with true condition is not correct > -------------------------------------------------- > > Key: TEIID-2500 > URL: https://issues.jboss.org/browse/TEIID-2500 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4, 7.7.8 > > > If a secondary searched case condition is always true, then the case will be inappropriately rewritten as just the then expression: > case when ... when true then x else y end > becomes just > x > However the prior cases should still be considered. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2598) 7.4 compatibility

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2598?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2598: --------------------------------- Fix Version/s: 7.7.8 > 7.4 compatibility > ----------------- > > Key: TEIID-2598 > URL: https://issues.jboss.org/browse/TEIID-2598 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Affects Versions: 7.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5, 7.7.8 > > > Exception result messages from a 7.4 and prior server are not handled correctly by 7.5+ clients and cause the connection to be dropped since the client assumes that it is not compatible. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2475) The RelationalNode.collectNodeStats is only subtracting out the last node

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2475?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2475: --------------------------------- Fix Version/s: 7.7.8 > The RelationalNode.collectNodeStats is only subtracting out the last node > ------------------------------------------------------------------------- > > Key: TEIID-2475 > URL: https://issues.jboss.org/browse/TEIID-2475 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.4, 7.7.8 > > Attachments: Query_Plan.txt > > > The "Node Cumulative Next Batch Process Time" Statistic > If you have a look at the explain plan (attached). Following the definition, > the JoinNode Node Cumulative Next Batch Process Time: 565471. So, it is the summation of AccessNode (Node Process Time: 892860) + DependentAccessNode (Node Process Time: 439) + JoinNode (Node Process Time: 2203120). The summation does not agree. > The RelationalNode.collectNodeStats looks wrong (it's effectively only subtracting out the last node) -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2608) Increase pg odbc client compatibility

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2608?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2608. ----------------------------------- Resolution: Done usage with the 9.0 driver with the appropriate options seems to work without exceptions now. > Increase pg odbc client compatibility > ------------------------------------- > > Key: TEIID-2608 > URL: https://issues.jboss.org/browse/TEIID-2608 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > Using a 9.0 level odbc client we see errors with the following: > set x TO y - since we don't expect TO > 'foo'::regclass - which is shorthand for an oid lookup > pg_index.indpred - is used by some metadata queries -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2610) pg protocol issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2610?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2610. ----------------------------------- Resolution: Done restructured the portal/cursor classes, normalized the result handling, and added more consistency with the protocol. Still did not address the notion that portals are transaction scoped though. > pg protocol issues > ------------------ > > Key: TEIID-2610 > URL: https://issues.jboss.org/browse/TEIID-2610 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5 > > > The primary issue is that closing a portal is also closing the prepared plan, which is causing a protocol error. -- 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

11 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2013