May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-554) searchability metadata should be type based

by Steven Hawkins (JIRA)

searchability metadata should be type based ------------------------------------------- Key: TEIID-554 URL: https://jira.jboss.org/jira/browse/TEIID-554 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.x Since searchability metadata is element based our check for (CapabilitiesUtil) gathers all elements in the expression - regardless of the type of the whole expression. This may be quite difficult to make this change in the existing metadata framework. -- 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

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIID-511) Make process plans serizializable.

by Steven Hawkins (JIRA)

Make process plans serizializable. ---------------------------------- Key: TEIID-511 URL: https://jira.jboss.org/jira/browse/TEIID-511 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.x Processing plans should be serializable to take advantage of replication and non-memory caches. See also TEIID-81 -- 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

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIID-513) Make the commandcontext available to the evaluatablevisitor

by Steven Hawkins (JIRA)

Make the commandcontext available to the evaluatablevisitor ----------------------------------------------------------- Key: TEIID-513 URL: https://jira.jboss.org/jira/browse/TEIID-513 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.x If the commandcontext is available to the evaluatablevisitor, then we can make a better decision about what determinism level to accept for planning function evaluation. -- 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

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-417) Add REST Support to Data Services

by Ted Jones (JIRA)

Add REST Support to Data Services --------------------------------- Key: TEIID-417 URL: https://jira.jboss.org/jira/browse/TEIID-417 Project: Teiid Issue Type: Feature Request Components: SOAP Services Reporter: Ted Jones Assignee: Ted Jones Need to add support for REST to data services. REST needs be enabled in Axis2 and a REST endpoint should be added to the data services WSDL. -- 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

12 years, 8 months

4
13
0 / 0

[JBoss JIRA] Created: (TEIID-586) Like pushdown handling

by Steven Hawkins (JIRA)

Like pushdown handling ---------------------- Key: TEIID-586 URL: https://jira.jboss.org/jira/browse/TEIID-586 Project: Teiid Issue Type: Bug Components: LDAP Connector, Query Engine, Salesforce Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 Both salesforce and ldap like semantics are not the same as SQL. We could capture this with more capabilities supportsLikeCaseSensitive and supportsLikeWildcardSingleCharacter repectively, or another approach would be to allow the connector to generically indicate partial support and have the query engine both push down the conjunct and leave a copy to be applied after the query. With either explicit supports or generic partial support it would only applicable to top level where clause conjuncts. -- 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

13 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-587) Better pushdown support for exotic joins

by Steven Hawkins (JIRA)

Better pushdown support for exotic joins ---------------------------------------- Key: TEIID-587 URL: https://jira.jboss.org/jira/browse/TEIID-587 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Our optimizations get in the way of Salesforce pushdown. Specifically rewriting like when possible to = and converting outer joins to inner joins. In both cases we would need to not perform the optimization in the first place or convert into an acceptable form prior to pushdown. The next is that salesforce, while requiring key criteria also allows other criteria in the left outer join on clause (which would be the same as having criteria on the nested relationship query in the salesforce query). With the capabilities as currently defined this would cause the query to not be pushed down. We should consider adding a relational supported join criteria type that requires key criteria but allows for outside criteria. Also we should treat the lack of inner join support to mean that criteria on the inner side of an outer join cannot be pushed. -- 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

13 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIID-536) Evaluate uncorrleated subqueries prior to pushdown for all command types.

by Steven Hawkins (JIRA)

Evaluate uncorrleated subqueries prior to pushdown for all command types. -------------------------------------------------------------------------- Key: TEIID-536 URL: https://jira.jboss.org/jira/browse/TEIID-536 Project: Teiid Issue Type: Feature Request Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.x Criteria and expressions containing uncorrelated subqueries that cannot be pushed down should be evaluated at the access node. Currently they require the introduction of a separate select node or will simply fail for insert/update/delete. See also JBEDSP-928 -- 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

13 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-464) Shared Installation Option

by Ramesh Reddy (JIRA)

Shared Installation Option -------------------------- Key: TEIID-464 URL: https://jira.jboss.org/jira/browse/TEIID-464 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 We need to decide if/how we're going to support the shared installation option. With the changes to what's stored in the metamatrix.properties (i.e., host properties and config.name), this now complicates how we'll install (i.e., system host setup and odbc) / support this feature. -- 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

13 years, 8 months

5
19
0 / 0

[JBoss JIRA] Created: (TEIID-597) AdminAPI method: UpdateProperties() needs to support updating the Service properties

by Van Halbert (JIRA)

AdminAPI method: UpdateProperties() needs to support updating the Service properties ------------------------------------------------------------------------------------- Key: TEIID-597 URL: https://jira.jboss.org/jira/browse/TEIID-597 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.1 Reporter: Van Halbert Assignee: Van Halbert The adminapi updateProperties(String identifier, String classname, Properties props) needs to support updating the Service properties. -- 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

13 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIID-358) Quick Start Guide / Examples needs to add derbyclient.jar to UDFs for previewing

by Paul Nittel (JIRA)

Quick Start Guide / Examples needs to add derbyclient.jar to UDFs for previewing -------------------------------------------------------------------------------- Key: TEIID-358 URL: https://jira.jboss.org/jira/browse/TEIID-358 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 6.0.0 Environment: fedora 10 Reporter: Paul Nittel Assignee: Steven Hawkins I ran into this while assisting user Bribek. When the Derby source is created and imported, a connector binding is built in the Designer. The one thing Designer does not do is place the jar file where it needs to be for previewing. The Quick Start Example needs to add the step of adding the derbyclient.jar file using the UDFs view and "Import UDF Extension Jar Files" action. IMHO, the Quick Start needs to be revisited to determine exactly what the required minimum effort is for a user to get through this. Perhaps on the Teiid side avoid all modeling and add a Quick Start on the Designer side that builds the VDB. If Teiid can do the Quick Start with just a VDB, that might be preferable. -- 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

13 years, 10 months

5
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009