February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-160) Remove redundant self-joins

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-160?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-160: ------------------------------- Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Remove redundant self-joins > --------------------------- > > Key: TEIID-160 > URL: https://jira.jboss.org/jira/browse/TEIID-160 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.x > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Query minimization should be used to remove self-joins on unique columns. This could be added as part of RuleRemoveOptionalJoins (but the rule may need to be run again after join planning). -- 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

15 years, 10 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 Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-159?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-159: ------------------------------- Component/s: Server Fix Version/s: 6.1.0 Affects Version/s: 6.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.x > Reporter: Jerry Helbling > Fix For: 6.1.0 > > > 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-208) LDAP Connector should implement Connection.isAlive(), in order to properly report connection status when monitored

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-208?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-208: --------------------------------- Component/s: LDAP Connector Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > LDAP Connector should implement Connection.isAlive(), in order to properly report connection status when monitored > ------------------------------------------------------------------------------------------------------------------ > > Key: TEIID-208 > URL: https://jira.jboss.org/jira/browse/TEIID-208 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Priority: Minor > Fix For: 6.1.0 > > > Connection.isAlive is currently implemented to always return "true". This means that connection status is not accurately reflected in the Console, and connection monitoring is not useful. We should implement this method, which may also require establishing a connection in the pool upon startup. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-157) mmadmin - Add a short start-up help text for users

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-157?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-157: ------------------------------- Component/s: Tools Fix Version/s: 6.1.0 Affects Version/s: 6.1.0 > mmadmin - Add a short start-up help text for users > -------------------------------------------------- > > Key: TEIID-157 > URL: https://jira.jboss.org/jira/browse/TEIID-157 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Affects Versions: 6.1.0 > Environment: All > Reporter: Paul Nittel > Assignee: Ramesh Reddy > Fix For: 6.1.0 > > > After watching John Verhaeg struggle with his initial use of mmadmin, it seems a short paragraph shouuld be displayed when mmadmin is executed. This could explain how to get help, basic usage, etc. > Also, if JAVA_HOME and/or SERVER_CLIENT aren't defined, is it possible for the startup to request this info, rather than asking the user to edit mmadmin? > We'd like this tool to live on, but it needs to be more user friendly. > PS: At no time did we actually enjoy laughing at John while he struggled, but it was kinda humorous. Seriously. Honest. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-155) Revisit TransformationMetadataFacade cache sizes

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-155?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-155: ------------------------------- Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Revisit TransformationMetadataFacade cache sizes > ------------------------------------------------ > > Key: TEIID-155 > URL: https://jira.jboss.org/jira/browse/TEIID-155 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.x > > > Defect Tracker #24593: Cases 5004 and 5835 have shown significant performance issues with resolving. While much of the performance impact was addressed with the 5.5 resolving refactor there is still a large performance hit for resolving that seems largely dependent upon metadata cache. We should investigate additional strategies (for example unified cache or writing more entries per index file read) as a way to increase performance. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-209) SalesForce Connector should support semi-join and anti-join pushdown upon release of 14.0 API

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-209?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-209: --------------------------------- Component/s: Salesforce Connector Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > SalesForce Connector should support semi-join and anti-join pushdown upon release of 14.0 API > --------------------------------------------------------------------------------------------- > > Key: TEIID-209 > URL: https://jira.jboss.org/jira/browse/TEIID-209 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Assignee: John Doyle > Fix For: 6.1.0 > > > SalesForce API 14.0 is adding support for semi-joins and anti-joins, e.g.: > SELECT Id, Name > FROM Account > WHERE Id IN > (SELECT AccountId FROM Opportunity WHERE StageName = 'Closed Lost') > Supporting pushdown in these situations could improve query performance dramatically in some cases. > It appears that the API puts a number of odd restrictions on the use of these "joins", which may make the implementation difficult. > See http://www.salesforce.com/us/developer/docs/api/index.htm for details (search the index for SOQL select). -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-156) Console should allow for setting arbitrary propeties

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-156?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-156: ------------------------------- Component/s: Console Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > Console should allow for setting arbitrary propeties > ---------------------------------------------------- > > Key: TEIID-156 > URL: https://jira.jboss.org/jira/browse/TEIID-156 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.1.0 > > > It would be especially useful for custom connectors, or even our own connectors with mid release enhancements, to allow the console to set arbitrary properties rather than requiring hand modification of the config. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-210) mmadmin should format XML documents

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-210?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-210: --------------------------------- Component/s: Tools Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > mmadmin should format XML documents > ----------------------------------- > > Key: TEIID-210 > URL: https://jira.jboss.org/jira/browse/TEIID-210 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Affects Versions: 6.0.0 > Environment: All supported client configurations: Linux and Windows > Reporter: Paul Nittel > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 6.1.0 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > We need a tool that will display XML document output formated in such a way that we can easily read it. > If we choose another tool, it should be capable of supporting this formating. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-212) Allow for server discovery to be restricted to URL hosts

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-212?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-212. -------------------------------- documentation changes will be handled under JBEDSP-534 > Allow for server discovery to be restricted to URL hosts > -------------------------------------------------------- > > Key: TEIID-212 > URL: https://jira.jboss.org/jira/browse/TEIID-212 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.0.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Server discovery prior to 6.0 was forced to be based upon server lists from the server. While this works well in intranets, there are times when customers may want to explicitly control which hosts are used (for example if they are using a custom load-balancing solution). -- 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

15 years, 10 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: --------------------------------- Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > 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.1.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

15 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009