August 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-784) Enhance distinct set op processing

by Steven Hawkins (JIRA)

Enhance distinct set op processing ---------------------------------- Key: TEIID-784 URL: https://jira.jboss.org/jira/browse/TEIID-784 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3.0 The sort operation should be able to pushed for each set op child (distinct is already eligible for pushing, but typically won't be because there's no order by). Also for union the sorted children should be fed directly into the second phase of sorting. All of this relies on the connector guaranteeing null ordering (TEIID-715 should be repurposed to cover the language enhancement of nulls first|last) -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1035) Replace Existing XML Document Functionality with other JBoss Technologies

by Ted Jones (JIRA)

Replace Existing XML Document Functionality with other JBoss Technologies ------------------------------------------------------------------------- Key: TEIID-1035 URL: https://jira.jboss.org/jira/browse/TEIID-1035 Project: Teiid Issue Type: Task Affects Versions: 7.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 8.0 The current XML Document homegrown technologies in the Teiid Designer with existing JBoss technologies. The following use cases should be satisfied: 1. Start with an XML Schema to build a Document that can be filled with relational, heterogeneous data and "shipped around" 2. Given an XML document/message definition, submit a query on the document with criteria defined within the document structure 3. Send an input document, produce and output document -- 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, 2 months

2
1
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

15 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIID-1209) Add cache usage statistics

by Steve Hawkins (JIRA)

Add cache usage statistics -------------------------- Key: TEIID-1209 URL: https://jira.jboss.org/browse/TEIID-1209 Project: Teiid Issue Type: Feature Request Components: Jopr Plugin, Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1.1 There are no cache statistics provided for the preparedplan or resultset caches. It would be good to show information on #of entries, hit ratio, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1066) Try to remove the Metadata Wrapper objects in the Client

by Ramesh Reddy (JIRA)

Try to remove the Metadata Wrapper objects in the Client -------------------------------------------------------- Key: TEIID-1066 URL: https://jira.jboss.org/jira/browse/TEIID-1066 Project: Teiid Issue Type: Task Components: AdminApi Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 7.0 There are few @MetadataMapper objects that convert from Managed object to the concrete object in the client code. These fail on regular basis when there is change to the class they are representing. Try to remove them and use built in reflection based methods. -- 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, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-1006) Dynamic vdb metadata load enhancements

by Steven Hawkins (JIRA)

Dynamic vdb metadata load enhancements -------------------------------------- Key: TEIID-1006 URL: https://jira.jboss.org/jira/browse/TEIID-1006 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Fix For: 7.1 Dynamic vdb metadata loading should have an admin or system function / call to reimport a particular source's metadata. The initial metadata loads should also be done in separate threads to prevent the caller from blocking (which is especially important if it's the deployer). -- 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, 2 months

2
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

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1214) The translators displayed in the JOPR console need a full description, not just Teiid Translator, because a 2 char. name (i.e., ws) with no description isn't clear

by Van Halbert (JIRA)

The translators displayed in the JOPR console need a full description, not just Teiid Translator, because a 2 char. name (i.e., ws) with no description isn't clear ------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1214 URL: https://jira.jboss.org/browse/TEIID-1214 Project: Teiid Issue Type: Bug Components: Jopr Plugin Reporter: Van Halbert Assignee: Steve Hawkins Priority: Minor The translators displayed in the JOPR console need a clear description, not just Teiid Translator, because a 2 char. name (i.e., ws) with essentially no description isn't clear. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-766) Oracle Spatial Connector is not utilizing function modifiers from Oracle Connector

by Larry O'Leary (JIRA)

Oracle Spatial Connector is not utilizing function modifiers from Oracle Connector ---------------------------------------------------------------------------------- Key: TEIID-766 URL: https://jira.jboss.org/jira/browse/TEIID-766 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.2.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Fix For: 6.2.0 When attempting to execute any functions that are supported by our Oracle connector implementation against the Oracle Spatial connector, invalid SQL is generated. This is due to com.metamatrix.connector.jdbc.oracle.spatial.OracleSpatialSQLTranslator.initialize(ConnectorEnvironment env) : void not calling its super.initialize(ConnectorEnvironment env) : void method. This call is required so that the parent (OracleSQLTranslator) can register its function modifiers. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-757) Oracle Spatial Connector is not properly adding ORDERED hint to SDO_RELATE function

by Larry O'Leary (JIRA)

Oracle Spatial Connector is not properly adding ORDERED hint to SDO_RELATE function ----------------------------------------------------------------------------------- Key: TEIID-757 URL: https://jira.jboss.org/jira/browse/TEIID-757 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0, 6.0.0, 6.2.0 Reporter: Larry O'Leary Assignee: Steven Hawkins Priority: Minor Oracle Spatial connector is rewriting a query that contains an SDO_RELATE() function using the ORDERED hint. The format/syntax of the hint does not conform to Oracle documentation. It does not appear this results in an error but I also have not verified that the ORDERED hint is actually getting used either. The following query: SELECT a.INTKEY FROM BQT1.SMALLA A, BQT1.SMALLB B WHERE sdo_relate(A.OBJECTVALUE, b.OBJECTVALUE, 'mask=ANYINTERACT') = true Is rewritten as: SELECT /* + ORDERED */A.IntKey FROM SmallA A, SmallB B WHERE SDO_RELATE(A.ObjectValue, B.ObjectValue, 'mask=ANYINTERACT') = 'true' Where as Oracle documentation seems to indicate that the query should actually be: SELECT /*+ ORDERED */ A.IntKey FROM SmallA A, SmallB B WHERE SDO_RELATE(A.ObjectValue, B.ObjectValue, 'mask=ANYINTERACT') = 'true' Notice the spacing in the hint as "SELECT_/*+_ORDERED_*/_A.IntKey..." instead of "SELECT_/*_+_ORDERED_*/A.IntKey..." -- 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, 2 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2010