February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-169) We should clarify the one-to-one relationship between Batch interface and BasicBatch class in the Connector API

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-169?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-169: ------------------------------- Component/s: Connector API Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > We should clarify the one-to-one relationship between Batch interface and BasicBatch class in the Connector API > ---------------------------------------------------------------------------------------------------------------- > > Key: TEIID-169 > URL: https://jira.jboss.org/jira/browse/TEIID-169 > Project: Teiid > Issue Type: Feature Request > Components: Connector API > Affects Versions: 6.0.0 > Reporter: Greg Haber > Assignee: Steven Hawkins > Priority: Optional > Fix For: 6.0.0 > > > When a connector implements the BatchedExecution interface, it is required to implement a method nextBatch() that returns a Batch. Batch is an interface, and technically can be implemented however the connector developer wants, as long as it implements "void addRow(List row)" and "List[] getResults()" - the implementation could theoretically store the current Batch state internally in a structure that was not a List[] and just do the needed conversions in these two methods. > However, in every known connector the implementation of BatchedExecution just uses the BasicBatch implementation we provide for Batch, which takes the straightforward path and stores the batch internally as an ArrayList. > This best practice is not obvious from the API itself (or even from the doc) - in the legacy MetaMatrix product we have had an instance where a developer built his own implementation of Batch (and somehow ran into trouble doing so). > Perhaps we should make this best practice more obvious - one thought is that Batch should be an abstract class rather than an interface - or perhaps BatchedExecution should require that nextBatch return BasicBatch or an extension of BasicBatch - or perhaps we should leave the API as is in this regard and just highlight this in the doc (and javadoc). -- 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-166) SalesForce connector should support "OrCriteria" and "NotCriteria"

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-166?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-166: ------------------------------- Component/s: Salesforce Connector Fix Version/s: 6.x Affects Version/s: 6.x > SalesForce connector should support "OrCriteria" and "NotCriteria" > ------------------------------------------------------------------ > > Key: TEIID-166 > URL: https://jira.jboss.org/jira/browse/TEIID-166 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.x > Environment: Windows 2003 Server, SF tech preview > Reporter: Michael Walker > Assignee: John Doyle > Fix For: 6.x > > > SalesForce SOQL supports "OR" and "NOT" criteria, but our connector does not. We should implement this functionality and add the capabilities, 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-167) Enhancement: Connector Developer's Kit needs overhaul

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-167?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-167: ------------------------------- Component/s: Connector API Documentation Fix Version/s: 6.x Affects Version/s: 6.x > Enhancement: Connector Developer's Kit needs overhaul > ----------------------------------------------------- > > Key: TEIID-167 > URL: https://jira.jboss.org/jira/browse/TEIID-167 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Documentation > Affects Versions: 6.x > Reporter: Ramesh Reddy > Assignee: John Doyle > Fix For: 6.x > > > Defect Tracker #24469: The CDK kit is based on the Command Shell framework, this needs to be moved to either MMSehll based or the Beanshell based framework, with better help system -- 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-163) Add classloader cache to embedded

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-163?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-163: ------------------------------- Component/s: Misc. Connectors Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > Add classloader cache to embedded > --------------------------------- > > Key: TEIID-163 > URL: https://jira.jboss.org/jira/browse/TEIID-163 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > The ConnectorService code for connector classpatch caching should be generalized for use in embedded. -- 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-165) Connector support for more converts

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-165?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-165: ------------------------------- Component/s: Misc. Connectors Fix Version/s: 6.1.0 Affects Version/s: 6.x > Connector support for more converts > ----------------------------------- > > Key: TEIID-165 > URL: https://jira.jboss.org/jira/browse/TEIID-165 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > > Defect Tracker #24822: Connector support for more converts (from object, clob, xml). Query changes are needed to remove the check from CapabilitiesUtil that is preventing the push down. Additionally defect 15144 should be worked. -- 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-195) JDBC Connector type should make "Password" property optional

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-195?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-195: --------------------------------- Component/s: JDBC Connector Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 Affects: [Release Notes] > JDBC Connector type should make "Password" property optional > ------------------------------------------------------------ > > Key: TEIID-195 > URL: https://jira.jboss.org/jira/browse/TEIID-195 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 6.0.0 > Reporter: Van Halbert > Priority: Minor > Fix For: 6.1.0 > > > The "username" and "password" properties of the JDBC connector binding should allow for null values. Some databases allow null passwords (and even null usernames). > Currently, Designer won't allow you to execute a VDB if password is blank. -- 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-196) Support creation of temp tables on physical sources.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-196?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-196: --------------------------------- Component/s: Connector API Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes] Complexity: High > Support creation of temp tables on physical sources. > ---------------------------------------------------- > > Key: TEIID-196 > URL: https://jira.jboss.org/jira/browse/TEIID-196 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ken Johnson > Fix For: 6.1.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. - 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-162) Delete and update support in temp table

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-162?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-162: ------------------------------- Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Delete and update support in temp table > --------------------------------------- > > Key: TEIID-162 > URL: https://jira.jboss.org/jira/browse/TEIID-162 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.x > > > Defect Tracker #23925: Delete and update are currently not supported in 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-198) lookup should work with virtual groups

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-198?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-198: --------------------------------- Component/s: Query Engine Updated documentation as well. > lookup should work with virtual groups > -------------------------------------- > > Key: TEIID-198 > URL: https://jira.jboss.org/jira/browse/TEIID-198 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.0.0 > > > lookup is currently restricted to non-virtual groups, but it should be allowed to use any group. Due to scoping issues though it's more practical to limit to only non-temporary groups. -- 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-198) lookup should work with virtual groups

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-198?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-198. -------------------------------- > lookup should work with virtual groups > -------------------------------------- > > Key: TEIID-198 > URL: https://jira.jboss.org/jira/browse/TEIID-198 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.0.0 > > > lookup is currently restricted to non-virtual groups, but it should be allowed to use any group. Due to scoping issues though it's more practical to limit to only non-temporary groups. -- 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