June 2010 - teiid-issues - Jboss List Archives

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

4
6
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, 7 months

3
6
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, 7 months

2
2
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, 7 months

2
3
0 / 0

[JBoss JIRA] Closed: (TEIID-500) Request for INSERT INTO...SELECT..FROM capability for virtual tables

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-500?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-500. ------------------------------- > Request for INSERT INTO...SELECT..FROM capability for virtual tables > -------------------------------------------------------------------- > > Key: TEIID-500 > URL: https://jira.jboss.org/browse/TEIID-500 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 6.2.0 > > > Per Issue Tracker ticket https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... . requesting the capability to use the INSERT INTO.. SELECT ..FROM syntax on virtual tables. > If this cannot be done, can a change be made to the SQL Validation to throw an exception. -- 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, 7 months

1
0
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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-758) Add locate function support to postgres

by Steven Hawkins (JIRA)

Add locate function support to postgres --------------------------------------- Key: TEIID-758 URL: https://jira.jboss.org/jira/browse/TEIID-758 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 6.2.0 Add support for locate to the postgresql translator. The 2 arg form is trival, but just as their jdbc escape docs indicate the 3 arg version needs more effort. For our purposes we'll use position('sub' in substr('string', fromIndex)). See TEIID-754 for possibly adding logic on the from index to ensure consistency with values less than 1. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-755) Oracle Connector is not honouring metadata when rewriting ORDER BY clause

by Larry O'Leary (JIRA)

Oracle Connector is not honouring metadata when rewriting ORDER BY clause ------------------------------------------------------------------------- Key: TEIID-755 URL: https://jira.jboss.org/jira/browse/TEIID-755 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 Fix For: 6.2.0 When executing a query that contains an ORDER BY clause, the Oracle Connector is rewriting the query using the column name given by the MM query rather than the source name as specified in the source model. What this means is that column name case is not being enforced. For example: MM User Command: SELECT INTKEY FROM BQT1.SMALLA UNION SELECT INTKEY FROM BQT1.SMALLB ORDER BY INTKEY Model represents INTKEY as IntKey for source name. Currently we rewrite as: SELECT SmallA.IntKey FROM SmallA UNION SELECT SmallB.IntKey FROM SmallB ORDER BY INTKEY This should actually be: SELECT SmallA.IntKey FROM SmallA UNION SELECT SmallB.IntKey FROM SmallB ORDER BY IntKey Although this does not trigger a failure with the current implementation, if the column names were qualified is SQL identifiers, the query would fail as Oracle is expecting a column name of "IntKey" and would not know what "INTKEY" was. -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-759) XQuery parameter evaluation fails

by Steven Hawkins (JIRA)

XQuery parameter evaluation fails --------------------------------- Key: TEIID-759 URL: https://jira.jboss.org/jira/browse/TEIID-759 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Non-constant xquery parameter evaluation is failing since the commandcontext is not used for the expression evaluation. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-775) Backwards scrolling defect

by Steven Hawkins (JIRA)

Backwards scrolling defect -------------------------- Key: TEIID-775 URL: https://jira.jboss.org/jira/browse/TEIID-775 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Iterating backwards does not work the since RequestWorkItem is setup to expect the end row as greater than the start row. It would be much simpler if the client were changed to issue the batch bounds with the lower value as the begin row. Clients may not have noticed this issue since they would have to do iteration beyond the third batch and then go backwards three batches. -- 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, 7 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010