June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1102) Create a replacement for the text translator

by Steve Hawkins (JIRA)

Create a replacement for the text translator -------------------------------------------- Key: TEIID-1102 URL: https://jira.jboss.org/browse/TEIID-1102 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors, Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.0 The current solution for the text connector requires the use of an external metadata file. This complicates the user experience with integrating text. An alternative approach would be to offer a built-in table function for text parsing: TEXTTABLE(expression COLUMNS column [, column]* [DELIMITER char] [(QUOTE|ESCAPE) char] [HEADER [integer]] [SKIP integer]) AS identifier column := identifier datatype [WIDTH integer] If width is specified for one column it must be specified for all columns. If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and HEADER should not be specified. expression - the text content to process, which should be convertable to CLOB. DELIMITER sets the field delimiter character to use. Defaults to ','. QUOTE sets the quote, or qualifier, character used to wrap field values. Defaults to '"'. ESCAPE sets the escape character to use if no quoting character is in use. This is used in situations where the delimiter or new line characters are escaped with a preceding character, e.g. \, HEADER specifies the text line number (counting every new line) on which the column names occur. All lines prior to the header will be skipped. If HEADER is specified, then the header line will be used to determine the TEXTTABLE column position by case-insensitive name matching. This is especially useful in situations where only a subset of the columns are needed. If the HEADER value is not specified, it defaults to 1. If HEADER is not specified, then columns are expected to match positionally with the text contents. SKIP specifies the number of text lines (counting every new line) to skip before parsing the contents. HEADER may still be specified with SKP. this would be implicitly a nested table, so it could be used to process multiple files: select x.* from t, texttable(t.clobcolumn COLUMNS first string, second date SKIP 1) x -- 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

14 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-739) JDBC Connector updates

by Steven Hawkins (JIRA)

JDBC Connector updates ---------------------- Key: TEIID-739 URL: https://jira.jboss.org/jira/browse/TEIID-739 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 The PostgreSQL translator should assume the use of a 8.0 jdbc client (supports back to the 7.2 server) so that we can remove DatePartFunctionModifer/ModifiedDatePartFunctionModifer also support for the bit functions should be added. The SQL Server translator / capabilities should be updated to assume the use of a 2005, DataDirect, or later driver (all support back to sql server 2000) so that support for most of the time functions can be added. -- 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

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1009) BQT Pushdown query "ORDER BY" is not always ordering results properly

by Warren Gibson (JIRA)

BQT Pushdown query "ORDER BY" is not always ordering results properly --------------------------------------------------------------------- Key: TEIID-1009 URL: https://jira.jboss.org/jira/browse/TEIID-1009 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Steven Hawkins Pushdown queries with "ORDER BY" are not always returning results in correct order. The below query is returning query results in the wrong order for Pushdown on DB2, MySql, Ora9-10-11, and SqlServer sources. If BQT1.SmallA.StringKey is placed in the SELECT clause the results are returned in the correct order. SELECT BQT1.SmallA.IntNum, BQT2.SmallB.StringNum FROM BQT1.SmallA, BQT2.SmallB WHERE BQT1.SmallA.IntNum = BQT2.SmallB.StringNum AND BQT1.SmallA.IntKey >= 5 AND BQT2.SmallB.IntKey >= 5 ORDER BY BQT1.SmallA.StringKey -- 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

14 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-1114) Add support for xmltable

by Steve Hawkins (JIRA)

Add support for xmltable ------------------------ Key: TEIID-1114 URL: https://jira.jboss.org/browse/TEIID-1114 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.0 We should add support for the xmltable table function to perform xml/relational mapping. -- 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

14 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1081) Provide pre built "Translator" for all the popular data sources

by Ramesh Reddy (JIRA)

Provide pre built "Translator" for all the popular data sources --------------------------------------------------------------- Key: TEIID-1081 URL: https://jira.jboss.org/jira/browse/TEIID-1081 Project: Teiid Issue Type: Sub-task Components: Build/Kits, JDBC Connector, LDAP Connector, Misc. Connectors Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Out of the box provide the pre-built "translators" for all the sources Teiid supports like - Oracle, SQLServer, MySQL etc. - Text - Loopback - LDAP - Sales Force - XML ?? -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-900) Refine option no cache behavior

by Steven Hawkins (JIRA)

Refine option no cache behavior ------------------------------- Key: TEIID-900 URL: https://jira.jboss.org/jira/browse/TEIID-900 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 Currently specifying option no cache with a particular group name cascades fully through all materialized views. It would be better if it only applied to a single level. Simply specifying option no cache without any specific groups would continue to behave the same way as it does currently, which bypasses cache for all materialized views. The materialized view scripts should be changed to SELECT ... INTO ... FROM x OPTION NOCACHE x so that the loads can take advantage of intermediate materialized view layers. -- 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

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-871) Refactor system vdb

by Steven Hawkins (JIRA)

Refactor system vdb ------------------- Key: TEIID-871 URL: https://jira.jboss.org/jira/browse/TEIID-871 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 6.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3 1. We should remove the system physical model - it's undocumented, exposes too much metadata cruft, and requires too much logic in the index connector to support it. 2. We should remove System.datatypeelements and System.datatypeelementproperties - the transformations are invalid (they will always return no rows) and they are redundant 3. There should be a new system table ProcedureParamProperties that exposes annotations for procedure params. with System.element/datatype and the corresponding properties tables. 4. This one is open to debate, but I would also like to remove System.describe - since annotations are available directly on the appropriate type table, there doesn't seem to be a good reason to introduce a procedure that operates over all metadata records to return the same information. -- 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

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-749) Replace the TestNoArgConnector Test with an integration test.

by John Doyle (JIRA)

Replace the TestNoArgConnector Test with an integration test. ------------------------------------------------------------- Key: TEIID-749 URL: https://jira.jboss.org/jira/browse/TEIID-749 Project: Teiid Issue Type: Task Components: XML Connector Affects Versions: 6.2.0 Reporter: John Doyle Assignee: John Doyle Priority: Minor Fix For: 6.2.0 -- 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

14 years, 6 months

2
5
0 / 0

[JBoss JIRA] Closed: (TEIID-143) Query should 'find' connector types and jars rather than have them predefined in the config.

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-143?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-143. ------------------------------- > Query should 'find' connector types and jars rather than have them predefined in the config. > -------------------------------------------------------------------------------------------- > > Key: TEIID-143 > URL: https://jira.jboss.org/browse/TEIID-143 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: Ramesh Reddy > Fix For: 7.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Currently, dqp as delived with Designer is preconfigured with connector types. I think it should discover the connectors that are available upon startup. This would make it easier to add connectors to a kit. The current process for adding a connector to a kit is manual and error prone. We have problems with it on nearly every release. > This is also an attractive feature for embedding query in other environments. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1075) Separate Connector Binding into Translation Layer and Connection Layer

by Ramesh Reddy (JIRA)

Separate Connector Binding into Translation Layer and Connection Layer ---------------------------------------------------------------------- Key: TEIID-1075 URL: https://jira.jboss.org/jira/browse/TEIID-1075 Project: Teiid Issue Type: Feature Request Components: Connector API, Query Engine Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Priority: Blocker Fix For: 7.0 Connector Binding = Translation Layer + Connection this association needs to be broken down into individual concerns as Translation Layer is concern of the Teiid and Connection semantics are more general purpose. By making this change Teiid configuration can be stable across deployment environments. Also, the translation layer then can be free of JCA semantics. The Connection layer then can be JCA Connection or provided by any Connection provider. -- 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

14 years, 6 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010