November 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-798) Add support for unknown keyword parsing

by Steven Hawkins (JIRA)

Add support for unknown keyword parsing --------------------------------------- Key: TEIID-798 URL: https://jira.jboss.org/jira/browse/TEIID-798 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 6.2.0 We already support the TRUE and FALSE keywords, we should add support for UNKNOWN as well. UNKNOWN is the same as convert(null, boolean). The stringtoboolean conversion should also support UNKNOWN. -- 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-800) Teiid char type should be consistently treated as char(1)

by Steven Hawkins (JIRA)

Teiid char type should be consistently treated as char(1) --------------------------------------------------------- Key: TEIID-800 URL: https://jira.jboss.org/jira/browse/TEIID-800 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.2.0 It looks like there was some initial design confusion with the Teiid character type in that it should map to the SQL char type (more specifically char(1)). However we added the restriction that an empty string produces an exception. This behavior is not supported by any database. To make the type consistent with sources and to allow for eventually supporting lengths other than 1, we should treat our char type as char(1) - for the stringtochar conversion we convert empty string to ' ' and the ascii function should return null for empty string (that's the common behavior for Sybase/SQL Server/Oracle but MySQL returns 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
2
0 / 0

[JBoss JIRA] Created: (TEIID-745) Ensure string parsing routines are consistent

by Steven Hawkins (JIRA)

Ensure string parsing routines are consistent --------------------------------------------- Key: TEIID-745 URL: https://jira.jboss.org/jira/browse/TEIID-745 Project: Teiid Issue Type: Quality Risk Components: Common, Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 String parsing strictness varies depending upon whether a convert or a parse function is used. In short we should: 1. Perform a trim prior to parsing (double and float converts already do this implicitly) 2. Use all non-whitespace characters in the parse string - the DateFormat, NumberFormat, and most of the convert methods allow for junk to appear after a successful parsing. 3. Time/Date/Timestamps should use non lenient parsing to disallow dates that are out of range, i.e. 2007-13-35 -- 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-797) The parser should use common conversion routines

by Steven Hawkins (JIRA)

The parser should use common conversion routines ------------------------------------------------ Key: TEIID-797 URL: https://jira.jboss.org/jira/browse/TEIID-797 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 The parser is using it's own logic for parsing escaped literals, it should instead use the common logic through DataTypeManager. -- 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-828) Default of 20 code tables is too small

by Steven Hawkins (JIRA)

Default of 20 code tables is too small -------------------------------------- Key: TEIID-828 URL: https://jira.jboss.org/jira/browse/TEIID-828 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 The default of 20 code tables of 10000 rows each is easily exhausted. It would be better to have max code tables, max records, and max records per table setting, which would allow for more tables, while still being conservative in the overall number of tables allowed. -- 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-684) Dynamic data integration feature (Integrate data with out a VDB)

by Ramesh Reddy (JIRA)

Dynamic data integration feature (Integrate data with out a VDB) ---------------------------------------------------------------- Key: TEIID-684 URL: https://jira.jboss.org/jira/browse/TEIID-684 Project: Teiid Issue Type: Feature Request Components: Connector API, Query Engine Reporter: Ramesh Reddy Assignee: Steven Hawkins Priority: Critical Fix For: 6.3.0 This is feature request for dynamically integrating the data with out any modelling exercise, so that any tooling is not required before you can start integrating data. Using this feature, the user would create/define a Connectors (data sources) in the Teiid runtime engine, and then user connects to runtime engine using the JDBC driver provided, then he/she can start writing SQL queries that spans multiple data sources in a single statement as if they are single source. For example: Data Source: A has TableA1 TableA2 DataSource: B has TableB1 TableB2 user can write SQL queries such as SELECT A.TableA1.e1, A.TableA1.e2, B.TableB1.e1, B.TableB1.e2 FROM A.TableA1, B.TableB1 WHERE A.TableA1.e1 = B.TableB1.e1 They can much more complex join queries than above too. -- 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
6
0 / 0

[JBoss JIRA] Created: (TEIID-614) Log XML Request/Response Doc binding property = TRUE is not causing documents to be logged.

by Ken Johnson (JIRA)

Log XML Request/Response Doc binding property = TRUE is not causing documents to be logged. -------------------------------------------------------------------------------------------- Key: TEIID-614 URL: https://jira.jboss.org/jira/browse/TEIID-614 Project: Teiid Issue Type: Bug Components: XML Connector Affects Versions: 6.0.0 Environment: Teiid 6.0.1 + Teiid Designer 6.0.0. RHEL 5. Teiid running both in Designer (SQL Explorer) and deployed as JDBC driver in JB AS 4.2.3. Reporter: Ken Johnson Assignee: Steven Hawkins XML (relational) SOAP Connector: Setting the "Log XML Request and Response Docs" binding property to true is failing to enable logging of SOAP request and response documents. -- 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

4
6
0 / 0

[JBoss JIRA] Created: (TEIID-787) Merge Oracle Spatial Connector functionality into Oracle Connector

by Larry O'Leary (JIRA)

Merge Oracle Spatial Connector functionality into Oracle Connector ------------------------------------------------------------------ Key: TEIID-787 URL: https://jira.jboss.org/jira/browse/TEIID-787 Project: Teiid Issue Type: Task Components: JDBC Connector Affects Versions: 6.2.0 Reporter: Larry O'Leary Assignee: Steven Hawkins It seems that the Oracle Spatial Connector is an extension of the Oracle Connector. Because it is an extension and the functionality, translators, capabilities, etc, are the same it means we need to manage the same connector in two different places not to mention have the same dependencies required and offered by two different packages. Because of this duplication, I recommend that the Oracle Spatial Connector be merged with the Oracle Connector. This should be as simple as merging the supported functions defined by the Oracle Spatial Connector with the Oracle Connector and migrating Oracle Spatial specific unit tests. Because the functions offered by the Oracle Spatial Connector are not system functions, the function definition for the Oracle Spatial functions should be kept separate and offered to the user as a post installation task if they choose to use spatial functions. For example, if a user decides to use Oracle as a data source, they would choose the Oracle Connector regardless of whether or not they planned on using spatial functions. The connector binding configuration would be the same in either case. If the user requires the use of the spatial functions, the only post-installation/configuration step would be to install the Oracle Spatial Function Definitions into their Teiid run-time environment or into Teiid Designer to make them available at design-time. -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIID-496) ValueValidationVisitor needs the variable context

by Steven Hawkins (JIRA)

ValueValidationVisitor needs the variable context ------------------------------------------------- Key: TEIID-496 URL: https://jira.jboss.org/jira/browse/TEIID-496 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 Resolving parameter values no longer sets the values directly on the command. The visitor will have to follow references to determine if the values are valid. -- 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-746) Composite keys should be detected by costing

by Steven Hawkins (JIRA)

Composite keys should be detected by costing -------------------------------------------- Key: TEIID-746 URL: https://jira.jboss.org/jira/browse/TEIID-746 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Detection of composite keys in costing logic has not worked since we break the criteria up prior to cost analysis. A possible fix for this is to also re-combine criteria that has been pushed to a source node - this approach will still fail to detect the key criteria if one of the conjuncts cannot be pushed. Also we should be able to detect disjunctive composite key usage more broadly. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2009