February 2011 - teiid-issues - Jboss List Archives

[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, 11 months

2
3
0 / 0

[JBoss JIRA] Updated: (TEIID-196) Support creation of temp tables on physical sources.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-196?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-196: --------------------------------- Fix Version/s: 9.0 (was: 8.0) Pushing to Teiid 9 > Support creation of temp tables on physical sources. > ---------------------------------------------------- > > Key: TEIID-196 > URL: https://issues.jboss.org/browse/TEIID-196 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ken Johnson > Fix For: 9.0 > > > This is a multi-part request. > First, the system should support creation of temporary tables using a physical backing store rather than buffer manger. Given multi-pass SQL's heavy use of temp tables, buffer manager can easily be overloaded with large interim results stored in temp tables. > Second, this should be a user-configurable behavior. For example, user might be able to choose a system-level or session-level default from among: > -- memory/cache > -- a source represented by a connector binding > -- a distinct temp source defined with it's own connection parameters (possibly another schema in the repository DB instance) > Ideally default selectoin should be override-able at temp table creation time through a DDL extension > In the case where multiple temp tables have been created on a source via connector, the query planner should recognize this and leverage pushdown to the temp store when later query passes access multiple temp tables. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1170) Support subqueries in temp table update/delete criteria

by Steve Hawkins (JIRA)

Support subqueries in temp table update/delete criteria ------------------------------------------------------- Key: TEIID-1170 URL: https://jira.jboss.org/browse/TEIID-1170 Project: Teiid Issue Type: Feature Request Affects Versions: 6.0.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Priority: Minor Fix For: 8.0 Subqueries are currently not supported in temp table update/delete criteria. -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Updated: (TEIID-964) Must pushdown functions in select clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-964?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-964: --------------------------------- Fix Version/s: 9.0 (was: 8.0) Pushing to Teiid 9 > Must pushdown functions in select clause > ---------------------------------------- > > Key: TEIID-964 > URL: https://issues.jboss.org/browse/TEIID-964 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Fix For: 9.0 > > > (F_ATM_REPORT_TYPE is a DB function) > SELECT F_ATM_REPORT_TYPE (BUS_LINE_CODE) FROM ... > Will not have the function pushed down if it only appears in the select clause. The planner must check if a function is pushdown only when it appears in the select clause and determine a source to push it to. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1462) Fully-qualified names should not be required when referencing procedures that have unique unqualified names

by Steven Hawkins (JIRA)

Fully-qualified names should not be required when referencing procedures that have unique unqualified names ----------------------------------------------------------------------------------------------------------- Key: TEIID-1462 URL: https://issues.jboss.org/browse/TEIID-1462 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Michael Walker Assignee: Steven Hawkins Priority: Minor Fix For: 7.0 This problem occurs in our transformation editor, and also occurs with real-time queries (e.g. from QueryBuilder/SQLExplorer, or any client). If you reference a non-qualified table name, e.g. "myTable", in a query, we'll attempt to resolve it if it is a unique name. Strangely, we don't do the same thing for virtual procedures, even if they are unique. Instead, you must use the fully-qualified name. There should be no disparity. This is a usability defect. This also happens to greatly extend the size of virtual procedure code, making it harder to read and debug. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-231) Ability to support Connector Level UDF functions in the System

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-231?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-231. ---------------------------------- Fix Version/s: 7.4 Resolution: Done ensured consistent qualification and pushdown naming of functions. allowed getPushdownFunctions to inject into SYS. ensured that schema specific functions have a pushdown check. > Ability to support Connector Level UDF functions in the System > -------------------------------------------------------------- > > Key: TEIID-231 > URL: https://issues.jboss.org/browse/TEIID-231 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 7.4, 7.3 > > > Currently we have UDF and Connector capabilities to define some custom functions in supported by a connector, however this is not seem less to deploy along with the connector, as connector functions do not support any parameters or design tools to define/declare them in CDK. We need a way to define and develop functions supported by a connector. > Suggestions. > 1) Use designer to define capabilities in a XMI file and attach with the connector, and let the server or MMQuery load these XMI files dynamically into the engine. > 2) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (TEIID-231) Ability to support Connector Level UDF functions in the System

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-231?page=com.atlassian.jira.plugin.... ] Steven Hawkins reopened TEIID-231: ---------------------------------- Assignee: Steven Hawkins (was: Ramesh Reddy) reopening for further refinements > Ability to support Connector Level UDF functions in the System > -------------------------------------------------------------- > > Key: TEIID-231 > URL: https://issues.jboss.org/browse/TEIID-231 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 7.3 > > > Currently we have UDF and Connector capabilities to define some custom functions in supported by a connector, however this is not seem less to deploy along with the connector, as connector functions do not support any parameters or design tools to define/declare them in CDK. We need a way to define and develop functions supported by a connector. > Suggestions. > 1) Use designer to define capabilities in a XMI file and attach with the connector, and let the server or MMQuery load these XMI files dynamically into the engine. > 2) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-43) command deterministic subqueries without from clauses should be merged if possible

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-43?page=com.atlassian.jira.plugin.s... ] Steven Hawkins resolved TEIID-43. --------------------------------- Fix Version/s: (was: 7.4) Resolution: Won't Fix In thinking about this more, the handling of uncorrelated subqueries should be sufficient to cover this issue for now. The other more general approaches including more aggressive join reordering or more pervasive constant propagation from literal view projections would be more beneficial for similar amounts of work. > command deterministic subqueries without from clauses should be merged if possible > ---------------------------------------------------------------------------------- > > Key: TEIID-43 > URL: https://issues.jboss.org/browse/TEIID-43 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > > Defect Tracker #24752: command deterministic subqueries without from clauses should be merged if possible: > i.e. select e1, a from pm1.g1, (select 1 a) x <=> select e1, 1 from pm1.g1 > i.e. select e1, (select 1 a) from pm1.g1 <=> select e1, 1 from pm1.g1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-147) Support for JAVA Stored Procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-147?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-147: --------------------------------- Fix Version/s: 9.0 (was: 8.0) pushing to 9.0 > Support for JAVA Stored Procedures > ---------------------------------- > > Key: TEIID-147 > URL: https://issues.jboss.org/browse/TEIID-147 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.x > Reporter: Ramesh Reddy > Fix For: 9.0 > > > Currently the Stored procedure support is lacking for both our procedure language and XQuery. Procedure support could be extended to java (or groovy) code, which will provide a powerful engine to execute a arbitrary queries. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-142) Introduce a mechanism to allow single source updates without an xa txn.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-142?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-142: --------------------------------- Fix Version/s: 9.0 (was: 8.0) pushing to 9.0 > Introduce a mechanism to allow single source updates without an xa txn. > ----------------------------------------------------------------------- > > Key: TEIID-142 > URL: https://issues.jboss.org/browse/TEIID-142 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 9.0 > > > Defect Tracker #24910: txnAutoWrap = OFF in 5.5 disables the use of local transactions. This was primarily done to support customers who 1. weren't paying for the transactional product > 2. weren't using an XA connection for an update > The concern of 1 goes away in 5.6 as all customers will have a transactional product. The secondary concern requires either a connection property that either ignores autocommit or the generic support of 1 phase commit on connectors supporting update and local transactions. The latter solution would allow non-XA aware connectors to seem XA aware as long as all updates went to a single source. Arjuna would also need to be configured to support the one phase commit optimization. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2011