July 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-171) Add SQLXML Function for Extract()

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-171?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-171: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Pushing to 6.3 > Add SQLXML Function for Extract() > --------------------------------- > > Key: TEIID-171 > URL: https://jira.jboss.org/jira/browse/TEIID-171 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.3.0 > > > We had a posting on the dev site (http://devcentral.metamatrix.com/node/2089809383) asking how they can retrieve an entire xml node from an input doc in a web service transformation instead of just the node text. Our current xPath function xPathValue() always return the text. We need something more like SQLXML extract()/extractvalue() so we can return the xml OR the text. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-239) ENHANCEMENT: Costing beyond cardinality sould be propogated

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-239?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-239: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Pushing to 6.3 > ENHANCEMENT: Costing beyond cardinality sould be propogated > ----------------------------------------------------------- > > Key: TEIID-239 > URL: https://jira.jboss.org/jira/browse/TEIID-239 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 6.3.0 > > > Defect Tracker #24037: Currently values for ndv and nnv are recalculated at each plan node based upon the value at the physical layer. This is not a good estimate. Instead, these values should be propagated through the plan just like the cardinality and adjusted appropriately for join, unions, etc. It may also be good to allow the use of costing metadata on virtual layers. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-211) subquery optimization

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-211?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-211: --------------------------------- Pushing to 6.3 > subquery optimization > --------------------- > > Key: TEIID-211 > URL: https://jira.jboss.org/jira/browse/TEIID-211 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.2.0 > > > Implement rewriter (and planner) optimizations for subqueries based upon semi and anti semi join capabilities. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-168) Remove resultset caching

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-168?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-168: --------------------------------- Pushing to 6.3 > Remove resultset caching > ------------------------ > > Key: TEIID-168 > URL: https://jira.jboss.org/jira/browse/TEIID-168 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector, Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.2.0 > > > Resultset caching should be replaced with relation and procedure caching. This would initially be backed by the buffermanager, based upon hints/costing, and be utilized by the planner rather than the resolver. It would be good if we also detected the level of determinism. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-239) ENHANCEMENT: Costing beyond cardinality sould be propogated

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-239?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-239: --------------------------------- Pushing to 6.3 > ENHANCEMENT: Costing beyond cardinality sould be propogated > ----------------------------------------------------------- > > Key: TEIID-239 > URL: https://jira.jboss.org/jira/browse/TEIID-239 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 6.2.0 > > > Defect Tracker #24037: Currently values for ndv and nnv are recalculated at each plan node based upon the value at the physical layer. This is not a good estimate. Instead, these values should be propagated through the plan just like the cardinality and adjusted appropriately for join, unions, etc. It may also be good to allow the use of costing metadata on virtual layers. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-171) Add SQLXML Function for Extract()

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-171?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-171: --------------------------------- Pushing to 6.3 > Add SQLXML Function for Extract() > --------------------------------- > > Key: TEIID-171 > URL: https://jira.jboss.org/jira/browse/TEIID-171 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.2.0 > > > We had a posting on the dev site (http://devcentral.metamatrix.com/node/2089809383) asking how they can retrieve an entire xml node from an input doc in a web service transformation instead of just the node text. Our current xPath function xPathValue() always return the text. We need something more like SQLXML extract()/extractvalue() so we can return the xml OR the text. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-159) Modify our handling of BigDecimal division to use MathContext.DECIMAL128 as our rounding mode to improve scale and precision of results

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-159?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-159: --------------------------------- Fix Version/s: 7.x (was: 6.2.0) Affects Version/s: 6.0.0 (was: 7.x) > Modify our handling of BigDecimal division to use MathContext.DECIMAL128 as our rounding mode to improve scale and precision of results > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-159 > URL: https://jira.jboss.org/jira/browse/TEIID-159 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Reporter: Jerry Helbling > Fix For: 7.x > > > Using MathContext.DECIMAL128 should give a more usable scale and precision to the results. > > Current behavior > 254403453878 / 21870000000 returns 12 > and > 254403453878.0001 / 21870000000 returns 11.6325 > > Improved behavior: > 254403453878 / 21870000000 returns 11.632531 > and > 254403453878.0001 / 21870000000 returns 11.632531 > > We should also investigate what the impact of this change will be on users who may be relying on our current behavior. > Reference: This enhancement was suggested by Issue Tracker Issue 175485, contributed by Greg Haber -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-721) JDBC Connection thru SQuirreL to Teiid Server instance not working

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-721?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-721. -------------------------------- Resolution: Done As all the classes where the Thread context class loader is used, we can safely replace with current class loader as all the resources that are being looked up will surely available in the same class loader as the loaded class. > JDBC Connection thru SQuirreL to Teiid Server instance not working > ------------------------------------------------------------------- > > Key: TEIID-721 > URL: https://jira.jboss.org/jira/browse/TEIID-721 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 6.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.2.0 > > > Caused by: java.lang.ClassNotFoundException: com.metamatrix.common.comm.platform.socket.client.AdminApiServerDiscovery > at java.net.URLClassLoader$1.run(URLClassLoader.java:200) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:247) > at com.metamatrix.core.util.ReflectionHelper.loadClass(ReflectionHelper.java:251) > at com.metamatrix.core.util.ReflectionHelper.create(ReflectionHelper.java:292) -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-251) Support SQL 2003 order by with expressions

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-251?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-251: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Even though this was recently requested by a customer, I'm pushing back to 6.3. We cannot directly support at the connector level since order by items only allow element or alias references. The workaround (which is what the patch implements in the rewriter) is to write the query in the for of select ... from (select ..., expr as x, expr as y ) ... order by ..., x, y > Support SQL 2003 order by with expressions > ------------------------------------------ > > Key: TEIID-251 > URL: https://jira.jboss.org/jira/browse/TEIID-251 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 6.3.0 > > Attachments: sort_expression.patch > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Defect Tracker #25000: SQL 2003 allows the order by clause to contain expressions instead of just simple simple symbol names. Since we already support expressions in the group by clause (which is actually against the SQL spec), it would make since to support expressions in the order by as well. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-251) Support SQL 2003 order by with expressions

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-251?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-251: --------------------------------- Attachment: sort_expression.patch Partial implementation of the sort expression feature. There is probably ~2 days of work left. > Support SQL 2003 order by with expressions > ------------------------------------------ > > Key: TEIID-251 > URL: https://jira.jboss.org/jira/browse/TEIID-251 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 6.2.0 > > Attachments: sort_expression.patch > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Defect Tracker #25000: SQL 2003 allows the order by clause to contain expressions instead of just simple simple symbol names. Since we already support expressions in the group by clause (which is actually against the SQL spec), it would make since to support expressions in the order by as well. -- 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

16 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2009