April 2010 - teiid-issues - Jboss List Archives

[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

15 years, 10 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-756) Oracle Connector is not producing the correct queries when using a LIMIT clause

by Larry O'Leary (JIRA)

Oracle Connector is not producing the correct queries when using a LIMIT clause ------------------------------------------------------------------------------- Key: TEIID-756 URL: https://jira.jboss.org/jira/browse/TEIID-756 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 When using a LIMIT clause in a query, the Oracle Connector rewrites it to something that Oracle will understand. The problem is that the rewritten version of the query is not returning the expected results. For example: SELECT INTKEY FROM BQT1.MEDIUMA LIMIT 50, 100 Should return 50 rows starting at row 100 but instead returns 0 rows when executed via the Oracle Connector. Currently the above query is rewritten as: SELECT * FROM (SELECT VIEW_FOR_LIMIT.*, ROWNUM ROWNUM_ FROM (SELECT MediumA.IntKey FROM MediumA) VIEW_FOR_LIMIT WHERE ROWNUM <= 150) WHERE ROWNUM_ > 50 Further more, the rewritten version of the query is also projecting a column named ROWNUM_ which would be invalid based on our query processing. -- 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

3
4
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

15 years, 10 months

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

15 years, 10 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

15 years, 10 months

3
4
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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Commented: (TEIID-207) Forward and Backward Compatibility of MetaMatrix JDBC Driver

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-207?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIID-207: -------------------------------------- The compatibility approach will be: 1. The compactobject stream logic will only omit descriptor information for non-primitive, non-externalizable classes. Since client and server may be running different vms we want to accurately convey the field information for serializable classes (many of which we don't control). It follows that any class that is just serializable will still write the full serialization information to the stream - which necessitates adding the serial version ids. 2. Our most commonly used externalizable classes will be built into the protocol to eliminate the need of even writing their full classnames as their descriptors (which makes it easier to refactor). See CompactObjectOutputStream where these classes are registered. 3. It follows from 2, that we'll use externalizable where ever possible. For the first cut this will include all non-admin api logic. The exteranizable contract will then be maintained so that it is backwards compatible - additional fields may be added though with any issues. 4. Other than adding additional fields, changes cannot be made that would alter result objects (ResultsMessage, ParameterInfo, PlanNode, etc.). If extensive changes are needed, then the server api will need to be changed to have additional DQP methods that return different results. The older method signatures will still be left in place though for older clients. > Forward and Backward Compatibility of MetaMatrix JDBC Driver > ------------------------------------------------------------ > > Key: TEIID-207 > URL: https://jira.jboss.org/jira/browse/TEIID-207 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: 7.0 > > > The MetaMatrix JDBC driver should be forward and backward compatible with newer/older versions of Enterprise Server. It is understood that certain protocol changes may break the compatibility but this should only happen in major releases and not affect Service Packs and maintenance releases. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-207) Forward and Backward Compatibility of MetaMatrix JDBC Driver

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-207?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-207: --------------------------------- Fix Version/s: 7.0 (was: 7.1) Putting back on 7.0, since we should strive to keep compatibility across all of 7.x > Forward and Backward Compatibility of MetaMatrix JDBC Driver > ------------------------------------------------------------ > > Key: TEIID-207 > URL: https://jira.jboss.org/jira/browse/TEIID-207 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: 7.0 > > > The MetaMatrix JDBC driver should be forward and backward compatible with newer/older versions of Enterprise Server. It is understood that certain protocol changes may break the compatibility but this should only happen in major releases and not affect Service Packs and maintenance releases. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-315) Add JDBC Connector developers guide

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-315?page=com.atlassian.jira.plug... ] Ramesh Reddy reassigned TEIID-315: ---------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Add JDBC Connector developers guide > ----------------------------------- > > Key: TEIID-315 > URL: https://jira.jboss.org/jira/browse/TEIID-315 > Project: Teiid > Issue Type: Sub-task > Components: Documentation > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 7.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

16 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2010