February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-194) LDAP Connector should be deterministic about what value is returned when an attribute is multi-valued

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-194?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-194: ------------------------------- Component/s: LDAP Connector Fix Version/s: 6.x Affects Version/s: 6.x > LDAP Connector should be deterministic about what value is returned when an attribute is multi-valued > ----------------------------------------------------------------------------------------------------- > > Key: TEIID-194 > URL: https://jira.jboss.org/jira/browse/TEIID-194 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.x > Reporter: Michael Walker > Priority: Minor > Fix For: 6.x > > > The LDAP connector returns only one result for a multi-valued attribute. It does not make any attempt to return the same value in a deterministic way, but should do so. -- 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-187) If the Datasource supports it, send the ANSI syntax in Source Query

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-187?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-187: ------------------------------- Component/s: Query Engine > If the Datasource supports it, send the ANSI syntax in Source Query > ------------------------------------------------------------------- > > Key: TEIID-187 > URL: https://jira.jboss.org/jira/browse/TEIID-187 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 6.0.0 > > > If the Datasource supports it, send the ANSI syntax in Source Query. > Reference Issue Tracker Ticket# 183202 -- 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-186) Expose catalog information and props in Connector API metadata [PEC]

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-186?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-186: ------------------------------- Component/s: Misc. Connectors Fix Version/s: 6.1.0 Affects Version/s: 6.x > Expose catalog information and props in Connector API metadata [PEC] > -------------------------------------------------------------------- > > Key: TEIID-186 > URL: https://jira.jboss.org/jira/browse/TEIID-186 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.1.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/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-188) Improve resolution of parameter references used in compare criteria

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-188?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-188: ------------------------------- Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Improve resolution of parameter references used in compare criteria > ------------------------------------------------------------------- > > Key: TEIID-188 > URL: https://jira.jboss.org/jira/browse/TEIID-188 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Mark Drilling > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.x > > Attachments: GregComments.txt > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Entering this JIRA from Issue 185605 in issue tracker. Greg Haber reports problem using Penrose off the shelf application. Example query as follows > select distinct petOwnersFromMM.owner, petOwnersFromMM.name from petVirtualDB.gregtest_virtual.gregtest.pet petOwnersFromMM where lower(petOwnersFromMM.owner) = lower(?) order by petOwnersFromMM.owner > He is getting "com.metamatrix.jdbc.MMSQLException: The function 'lower(?)' has more than one possible signature." since the lower function is ambiguous. > Workaround is to use "lower(convert(?, string))" in the sql. There is a statement in the release notes for a future enhancement that we could use the type info from the other side of the compare criteria to determine what the type should be. > I will attach Gregs further comments for reference. -- 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-189) Temp tables should maintain their costing metadata

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-189?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-189: ------------------------------- Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Temp tables should maintain their costing metadata > -------------------------------------------------- > > Key: TEIID-189 > URL: https://jira.jboss.org/jira/browse/TEIID-189 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.x > > > Defect Tracker #24522: Temp table cardinality is currently only used for staging tables. It would also be generally useful for ad hoc queries to have the TempTableStoreImpl maintain the cardinality of the tables. Other costing information could actually be incorrect now (such as column min/max) depending upon what has been selected into a temp table. -- 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-185) Add Option For MTOM in Web Services

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-185?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-185: ------------------------------- Component/s: SOAP Services Fix Version/s: 7.x Affects Version/s: 6.x > Add Option For MTOM in Web Services > ----------------------------------- > > Key: TEIID-185 > URL: https://jira.jboss.org/jira/browse/TEIID-185 > Project: Teiid > Issue Type: Feature Request > Components: SOAP Services > Affects Versions: 6.x > Reporter: Ted Jones > Assignee: Ted Jones > Priority: Optional > Fix For: 7.x > > > Defect Tracker #24316: It would be great if we could add an option for Enterprise Web Service users to use Message Transmission Optimization Mechanism (MTOM). This would provide a means for them to handle very large result sets without the memory implications. -- 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-181) Allow connectors to request replanning of source query by throwing an exception

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-181?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-181: ------------------------------- Component/s: Connector API Query Engine > Allow connectors to request replanning of source query by throwing an exception > ------------------------------------------------------------------------------- > > Key: TEIID-181 > URL: https://jira.jboss.org/jira/browse/TEIID-181 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Reporter: Greg Haber > Assignee: Steven Hawkins > Priority: Minor > > In FEDERATE-126 more granular connector capabilities were requested, for supporting sources that don't follow traditional relational capability patterns (especially SFDC). > The level of effort for such a request is presumably fairly high for the DQP component, since it needs to have additional logic added to understand the new capability and to modify the planning process to take them into account. > It occurred to me that a general purpose backup mechanism would be for connectors to have the ability after getting a query they couldn't handle, to throw a new type of exception (perhaps ReplanRequestException), which would contain information about what connector capabilities should be excluded from the replanning process. Then the planner would come up with a new plan, and make new source query/queries based off that new plan. > For example take the case of SFDC, which handles outer joins (left or right, but not full) but not inner joins (and for the sake of argument say that FEDERATE-126 and FEDERATE-114 were not implemented). The SFDC connector gets sent a query with an inner join. It then throws an exception requesting a replan, this time with no join pushdown. Then the planner replans this as without join pushdown, and resubmits the query (or in many cases multiple queries). > Now, one big question here is, does replanning mean replanning the entire federated query, or just redoing that one source query? The former would give a more efficient overall plan, but it may be too late to do this (other connectors may already be at work). For the former to work, I would think we would need to have an additional step in the connector framework to run the proposed query plan by all the connectors before actually executing anything, which would be additional overhead on all queries, not the small subset for which this problem exists. So maybe the latter (redoing that one source query) is the only reasonable alternative. > A workaround with similar results is FEDERATE-114 style stuff (tell the consumer what was wrong, and ask them to override connector capabilities in a new query. But that has the same general inefficiency of an automatic replanning of the entire federated query. So it would not be as nice as replanning just one source query. -- 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-182) Change client SSL configuration to be based upon the classpath

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-182?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-182: ------------------------------- Component/s: Common > Change client SSL configuration to be based upon the classpath > -------------------------------------------------------------- > > Key: TEIID-182 > URL: https://jira.jboss.org/jira/browse/TEIID-182 > Project: Teiid > Issue Type: Feature Request > Components: Common > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > > The current strategy of relying on -D jvm options for SSL cause users to edit launching scripts, which should otherwise not need changed. It also causes there to be only a global set of settings. It would be better to driver the SSL and potentially other client settings off of a properties file in the classpath. -- 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-183) user "or" and "in" criteria should generate multiple queries in some situations

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-183?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-183: ------------------------------- Component/s: Query Engine Fix Version/s: 7.x Affects Version/s: 6.x > user "or" and "in" criteria should generate multiple queries in some situations > ------------------------------------------------------------------------------- > > Key: TEIID-183 > URL: https://jira.jboss.org/jira/browse/TEIID-183 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 7.x > > > Defect Tracker #23857: Since web services and relational wrappers around procedures do not support "in" or "or" criteria, an enhancement would be union the results of multipe queries rather than not pushing down the criteria or not validating the query entirely. -- 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-184) Add support for coalesce and nullif

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-184?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-184: ------------------------------- Component/s: Query Engine > Add support for coalesce and nullif > ----------------------------------- > > Key: TEIID-184 > URL: https://jira.jboss.org/jira/browse/TEIID-184 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Coalesce and nullif are SQL standard functions that can be implemented in the rewriter as case functions. -- 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