November 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Moved: (TEIID-886) Request for more statistical functions in MetaMatrix

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-886?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1129 to TEIID-886: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-886 (was: JBEDSP-1129) Fix Version/s: (was: 5.5.4) > Request for more statistical functions in MetaMatrix > ---------------------------------------------------- > > Key: TEIID-886 > URL: https://jira.jboss.org/jira/browse/TEIID-886 > Project: Teiid > Issue Type: Feature Request > Reporter: Debbie Steigner > > Please provide a richer set of aggregate functions, specifically statistical functions like population standard deviation, sample standard deviation, population standard variance, etc. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-885) CTC vdbs should use appropriate capabilities

by Warren Gibson (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-885?page=com.atlassian.jira.plug... ] Warren Gibson updated TEIID-885: -------------------------------- Component/s: Integration Tests > CTC vdbs should use appropriate capabilities > -------------------------------------------- > > Key: TEIID-885 > URL: https://jira.jboss.org/jira/browse/TEIID-885 > Project: Teiid > Issue Type: Quality Risk > Components: Integration Tests > Reporter: Steven Hawkins > Assignee: Warren Gibson > > The CTC test vdbs currently use SimpleCapabilities rather than the actual source capabilities. This means that very little push down support is ever tested by CTC. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Reopened: (TEIID-885) CTC vdbs should use appropriate capabilities

by Warren Gibson (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-885?page=com.atlassian.jira.plug... ] Warren Gibson reopened TEIID-885: --------------------------------- Was not fixed in 5.5.4 > CTC vdbs should use appropriate capabilities > -------------------------------------------- > > Key: TEIID-885 > URL: https://jira.jboss.org/jira/browse/TEIID-885 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Warren Gibson > > The CTC test vdbs currently use SimpleCapabilities rather than the actual source capabilities. This means that very little push down support is ever tested by CTC. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-885) CTC vdbs should use appropriate capabilities

by Warren Gibson (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-885?page=com.atlassian.jira.plug... ] Warren Gibson moved JBEDSP-950 to TEIID-885: -------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-885 (was: JBEDSP-950) Component/s: (was: Testing) Fix Version/s: (was: 5.5.4) Affects Version/s: (was: 5.5.3) > CTC vdbs should use appropriate capabilities > -------------------------------------------- > > Key: TEIID-885 > URL: https://jira.jboss.org/jira/browse/TEIID-885 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Warren Gibson > > The CTC test vdbs currently use SimpleCapabilities rather than the actual source capabilities. This means that very little push down support is ever tested by CTC. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-145) Parse double quoted literals as identifiers by default

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-145?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-145. ---------------------------------- Resolution: Done allowDoubleQuotedVariable is now defaulted to true. There may need to be other ways to specify setting the value to false (such as a system property), so that the behavior may be changed globally (or on a per vdb basis for legacy) and not just for the user command . > Parse double quoted literals as identifiers by default > ------------------------------------------------------ > > Key: TEIID-145 > URL: https://jira.jboss.org/jira/browse/TEIID-145 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.0 > > > The allowDoubleQuotedVariable property should default to true, rather than false. > Need to make a special note of this in release notes. An unknown number of unit tests will be affected. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-145) Parse double quoted literals as identifiers by default

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-145?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-145: --------------------------------- Component/s: Query Engine > Parse double quoted literals as identifiers by default > ------------------------------------------------------ > > Key: TEIID-145 > URL: https://jira.jboss.org/jira/browse/TEIID-145 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.0 > > > The allowDoubleQuotedVariable property should default to true, rather than false. > Need to make a special note of this in release notes. An unknown number of unit tests will be affected. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-145) Parse double quoted literals as identifiers by default

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-145?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-145: --------------------------------- Fix Version/s: 7.0 (was: 6.0.0) > Parse double quoted literals as identifiers by default > ------------------------------------------------------ > > Key: TEIID-145 > URL: https://jira.jboss.org/jira/browse/TEIID-145 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.0 > > > The allowDoubleQuotedVariable property should default to true, rather than false. > Need to make a special note of this in release notes. An unknown number of unit tests will be affected. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Reopened: (TEIID-145) Parse double quoted literals as identifiers by default

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-145?page=com.atlassian.jira.plug... ] Steven Hawkins reopened TEIID-145: ---------------------------------- Now that the system transformations have been removed, there's no built-in usage of double quoted literal. It should be fine to change the default to double quoted identifiers and only have legacy users worry about setting the parser to support double quoted literal. > Parse double quoted literals as identifiers by default > ------------------------------------------------------ > > Key: TEIID-145 > URL: https://jira.jboss.org/jira/browse/TEIID-145 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > > The allowDoubleQuotedVariable property should default to true, rather than false. > Need to make a special note of this in release notes. An unknown number of unit tests will be affected. -- 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, 6 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-694?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-694. ---------------------------------- Resolution: Duplicate Issue Dup of TEIID-695 > Equality comparison of JoinPredicate returns true even when JoinPredicate criteria is different > ----------------------------------------------------------------------------------------------- > > Key: TEIID-694 > URL: https://jira.jboss.org/jira/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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-693?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-693. ---------------------------------- Resolution: Duplicate Issue Dup of TEIID-695 > Equality comparison of JoinPredicate returns true even when JoinPredicate criteria is different > ----------------------------------------------------------------------------------------------- > > Key: TEIID-693 > URL: https://jira.jboss.org/jira/browse/TEIID-693 > 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2009