June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-694) Equality comparison of JoinPredicate returns true even when JoinPredicate criteria is different

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-694?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-694. ------------------------------- > Equality comparison of JoinPredicate returns true even when JoinPredicate criteria is different > ----------------------------------------------------------------------------------------------- > > Key: TEIID-694 > URL: https://jira.jboss.org/browse/TEIID-694 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Priority: Minor > Fix For: 6.2.0 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > When comparing the following command objects the commands evaluate as equal when performing c1.equals(c2) even though the criteria is different in the two commands: > c1 = SELECT bqt1.smalla.intkey, bqt1.smallb.intkey, bqt1.smalla.intnum, bqt1.smallb.intnum FROM bqt1.smalla LEFT OUTER JOIN bqt1.smallb ON bqt1.smalla.intkey = bqt1.smallb.intkey AND bqt1.smallb.intnum = 1 > c2 = SELECT bqt1.smalla.intkey, bqt1.smallb.intkey, bqt1.smalla.intnum, bqt1.smallb.intnum FROM bqt1.smalla LEFT OUTER JOIN bqt1.smallb ON bqt1.smalla.intkey = bqt1.smallb.intkey > This is due to the method com.metamatrix.query.sql.lang.JoinPredicate.equals(Object obj) referencing itself when getting the criteria from itself and the obj being passed in: > ... > List thisCrit = this.getJoinCriteria(); > ... > List otherCrit = this.getJoinCriteria(); > ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-879) validate min/max non-comparable

by Steven Hawkins (JIRA)

validate min/max non-comparable ------------------------------- Key: TEIID-879 URL: https://jira.jboss.org/jira/browse/TEIID-879 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 6.3 min and max aggregates are currently not validated to ensure that they operate on only comparable types. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-849) subquery as input to procedure fails

by Steven Hawkins (JIRA)

subquery as input to procedure fails ------------------------------------ Key: TEIID-849 URL: https://jira.jboss.org/jira/browse/TEIID-849 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3.0 A subquery as an input to a procedure (exec) will fail because it is never resolved. Also within the scope of a procedure something like: select e1 into #t1 from pm1.g1; select e2 from (exec pm1.sq2((select max(e1) from #t1))) x; will fail since the temp table store is not known inside the procedure plan that is evaluating the input parameters. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-41) Non selectable columns should be omitted from metadata

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-41?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins closed TEIID-41. ------------------------------ > Non selectable columns should be omitted from metadata > ------------------------------------------------------ > > Key: TEIID-41 > URL: https://jira.jboss.org/browse/TEIID-41 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Fix For: 7.0 > > > Defect Tracker #24612: Non-selectable columns should not be visible in metadata. When visible they will lead to invalid sql getting generated (there was a SQL Explorer defect to that effect, but I can't find it at this time). This is not a regression in 5.5 in 5.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-880) SQL Server uniqueidentifier handling

by Steven Hawkins (JIRA)

SQL Server uniqueidentifier handling ------------------------------------ Key: TEIID-880 URL: https://jira.jboss.org/jira/browse/TEIID-880 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 6.3 SQL Server's uniqueidentifier is typically imported as a string, but cannot be used in comparable operations (distinct, order by, group by). Our designer cost analyzer logic already compensated for this, but a more general fix would be to wrap the uniqueidentifier as cast(col as char(36)), which would be safe. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-222) Procedural relational execution should support disjunctive criteria

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-222?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-222. ------------------------------- > Procedural relational execution should support disjunctive criteria > ------------------------------------------------------------------- > > Key: TEIID-222 > URL: https://jira.jboss.org/browse/TEIID-222 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.0 > > > Defect Tracker #24820: Disjunctive criteria should be supported for procedure execution, i.e. select * from proc where input1 = 1 or input2 = 2. Note that for this to work it will to know the possible values for missing parameters in each of the disjuncts, which is covered by defect 24821. Otherwise each disjunct must fully specify all parameters, i.e. (input1 = 1 and input2 = 2) or (input1 = 2 and input2 = 3) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-186) Expose catalog information and props in Connector API metadata [PEC]

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-186?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-186. ------------------------------- > Expose catalog information and props in Connector API metadata [PEC] > -------------------------------------------------------------------- > > Key: TEIID-186 > URL: https://jira.jboss.org/browse/TEIID-186 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 7.0 > > > Defect Tracker #20304: This request is to expose information on catalogs and schemas in relational models as separate entities and also to expose extension properties on those entities. Currently, only models and groups exist in runtime indexes and Connector API metadata and catalogs and schemas are just treated as namespace elements for groups. The XML Connector uses those catalogs and would like to store extension properties on them and retrieve those in the connector. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-830) AdminShell row count is not accurate

by Steven Hawkins (JIRA)

AdminShell row count is not accurate ------------------------------------ Key: TEIID-830 URL: https://jira.jboss.org/jira/browse/TEIID-830 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 6.0.0 Reporter: Steven Hawkins Priority: Optional Fix For: 6.3.0 AdminShell reports rows produced as the number of lines, so it is off for xml or any string containing new lines. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-845) AdminShell needs to be able to produce and display a Query Plan

by Paul Nittel (JIRA)

AdminShell needs to be able to produce and display a Query Plan --------------------------------------------------------------- Key: TEIID-845 URL: https://jira.jboss.org/jira/browse/TEIID-845 Project: Teiid Issue Type: Feature Request Components: Tools Affects Versions: 6.2.0 Reporter: Paul Nittel Assignee: Steven Hawkins AdminShell needs to be able to produce and display query plans for the user. Since QueryBuilder is no more, the Designer is the only mechanism we have to produce query plans. That may not always be possible or convenient for the user, so I'd like to see this ability added to the adminAPI / AdminShell. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-563) Exporting the configuration, via console or utility, the configuration system properties now contains everything in the system, not just defined by the Configuration component type

by Van Halbert (JIRA)

Exporting the configuration, via console or utility, the configuration system properties now contains everything in the system, not just defined by the Configuration component type ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: TEIID-563 URL: https://jira.jboss.org/jira/browse/TEIID-563 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Steven Hawkins When exporting the configuration, using either the console or the configexport utility, the configuration properties segment now contains all the properties that exist when calling System.getProperties(), instead only what is defined by the Configuration component type. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010