November 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-766) Oracle Spatial Connector is not utilizing function modifiers from Oracle Connector

by Larry O'Leary (JIRA)

Oracle Spatial Connector is not utilizing function modifiers from Oracle Connector ---------------------------------------------------------------------------------- Key: TEIID-766 URL: https://jira.jboss.org/jira/browse/TEIID-766 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.2.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Fix For: 6.2.0 When attempting to execute any functions that are supported by our Oracle connector implementation against the Oracle Spatial connector, invalid SQL is generated. This is due to com.metamatrix.connector.jdbc.oracle.spatial.OracleSpatialSQLTranslator.initialize(ConnectorEnvironment env) : void not calling its super.initialize(ConnectorEnvironment env) : void method. This call is required so that the parent (OracleSQLTranslator) can register its function modifiers. -- 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

13 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-757) Oracle Spatial Connector is not properly adding ORDERED hint to SDO_RELATE function

by Larry O'Leary (JIRA)

Oracle Spatial Connector is not properly adding ORDERED hint to SDO_RELATE function ----------------------------------------------------------------------------------- Key: TEIID-757 URL: https://jira.jboss.org/jira/browse/TEIID-757 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 Oracle Spatial connector is rewriting a query that contains an SDO_RELATE() function using the ORDERED hint. The format/syntax of the hint does not conform to Oracle documentation. It does not appear this results in an error but I also have not verified that the ORDERED hint is actually getting used either. The following query: SELECT a.INTKEY FROM BQT1.SMALLA A, BQT1.SMALLB B WHERE sdo_relate(A.OBJECTVALUE, b.OBJECTVALUE, 'mask=ANYINTERACT') = true Is rewritten as: SELECT /* + ORDERED */A.IntKey FROM SmallA A, SmallB B WHERE SDO_RELATE(A.ObjectValue, B.ObjectValue, 'mask=ANYINTERACT') = 'true' Where as Oracle documentation seems to indicate that the query should actually be: SELECT /*+ ORDERED */ A.IntKey FROM SmallA A, SmallB B WHERE SDO_RELATE(A.ObjectValue, B.ObjectValue, 'mask=ANYINTERACT') = 'true' Notice the spacing in the hint as "SELECT_/*+_ORDERED_*/_A.IntKey..." instead of "SELECT_/*_+_ORDERED_*/A.IntKey..." -- 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

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-751) SDO_WITHIN_DISTANCE function of Oracle Spatial Connector is pushing string literal to data source

by Larry O'Leary (JIRA)

SDO_WITHIN_DISTANCE function of Oracle Spatial Connector is pushing string literal to data source ------------------------------------------------------------------------------------------------- Key: TEIID-751 URL: https://jira.jboss.org/jira/browse/TEIID-751 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0, 6.0.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Priority: Minor Fix For: 6.2.0 Executing a query which uses the SDO_WITHIN_DISTANCE function in criteria results in an invalid query being sent to Oracle. Query: SELECT RECORD_ID FROM OraSpatialSrcTable WHERE sdo_within_distance(MARKER, '(SDO_GEOMETRY(2001, 8307, MDSYS.SDO_POINT_TYPE(90.0, -45.0, NULL), NULL, NULL))', "DISTANCE=25.0 UNIT=NAUT_MILE") = 'TRUE' Results In Exception: ERROR <com.metamatrix.core|0> [MetaMatrix][Oracle JDBC Driver][Oracle]ORA-29900: operator binding does not exist ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_WITHIN_DISTANCE' Executing statement: SELECT ORASPATIALSRCTABLE.RECORD_ID FROM ORASPATIALSRCTABLE WHERE SDO_WITHIN_DISTANCE(ORASPATIALSRCTABLE.MARKER, '(SDO_GEOMETRY(2001, 8307, MDSYS.SDO_POINT_TYPE(90.0, -45.0, NULL), NULL, NULL))', 'DISTANCE=25.0 UNIT=NAUT_MILE') = TRUE java.sql.SQLException: [MetaMatrix][Oracle JDBC Driver][Oracle]ORA-29900: operator binding does not exist ORA-06553: PLS-306: wrong number or types of arguments in call to 'SDO_WITHIN_DISTANCE' at com.metamatrix.common.util.exception.SQLExceptionUnroller.unRollException(SQLExceptionUnroller.java:43) at com.metamatrix.connector.jdbc.JDBCBaseExecution.createError(JDBCBaseExecution.java:147) at com.metamatrix.connector.jdbc.JDBCBaseExecution.createAndLogError(JDBCBaseExecution.java:103) at com.metamatrix.connector.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:89) at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:274) at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processBatchRequest(ConnectorWorker.java:165) at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:139) at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:51) The exception is due to the second parameter of SDO_WITHIN_DISTANCE being escaped as a string. The expected query should be: SELECT ORASPATIALSRCTABLE.RECORD_ID FROM ORASPATIALSRCTABLE WHERE SDO_WITHIN_DISTANCE(ORASPATIALSRCTABLE.MARKER, (SDO_GEOMETRY(2001, 8307, MDSYS.SDO_POINT_TYPE(90.0, -45.0, NULL), NULL, NULL)), 'DISTANCE=25.0 UNIT=NAUT_MILE') = TRUE In the above query the first parameter was an element of type String. If the first parameter was of type Object, the function is rewritten correctly. This appears to be primarily due to the function signatures of sdo_within_distance and the query rewriter performing an implicit convert on the second parameter to make it match the function signature of String, Object, String rather than Object, String, String. -- 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

13 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-829) revamp code table caching

by Steven Hawkins (JIRA)

revamp code table caching ------------------------- Key: TEIID-829 URL: https://jira.jboss.org/jira/browse/TEIID-829 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.3.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3.0 Code tables have several design issues: 1. the cache should allow for eviction and possibly expiration. 2. the cache should be backed by the common caching facility. 3. should allow for explicit scoping - at a minimum global vs. vdb, but additional may be good to allow session and request. 4. the implementation should be minimally blocking (in terms of both query execution and use of synchronization). -- 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

13 years, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIID-860) Add odbc support

by Steven Hawkins (JIRA)

Add odbc support ---------------- Key: TEIID-860 URL: https://jira.jboss.org/jira/browse/TEIID-860 Project: Teiid Issue Type: Feature Request Components: Query Engine, Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3 Support for ODBC should be added to the server. H2 has an emulation mode for pg odbc that could serve as our template as well. Just like the OA system tables, we would need to add pg system tables (possibly adding a mechanism to inject additional system vdbs, rather than adding more tables to the system.vdb). Clients would use http://www.postgresql.org/ftp/odbc/versions/ -- 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

13 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIID-872) Add Teiid 6.2 release binaries in the JBoss Maven repository

by Ramesh Reddy (JIRA)

Add Teiid 6.2 release binaries in the JBoss Maven repository ------------------------------------------------------------ Key: TEIID-872 URL: https://jira.jboss.org/jira/browse/TEIID-872 Project: Teiid Issue Type: Task Components: Build/Kits Affects Versions: 6.2.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Priority: Minor Add 6.2 release to the JBoss Maven repository at http://repository.jboss.com/maven2/org/jboss/teiid/ -- 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

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-874) Wiki documentation on SSL Encryption is misleading

by Nestor D. Rodriguez (JIRA)

Wiki documentation on SSL Encryption is misleading -------------------------------------------------- Key: TEIID-874 URL: https://jira.jboss.org/jira/browse/TEIID-874 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 6.2.0 Environment: N/A Reporter: Nestor D. Rodriguez Assignee: Steven Hawkins Priority: Minor The wiki page describing how to implement SSL in Teiid (https://www.jboss.org/community/wiki/secureclientconnectionsusingsslinteiid) implies that the keystore and trustore password properties (ssl.keystore.Password and ssl.truststore.Password) can be entered in cleartext. The code, on the other hand, requires them to be encrypted, using the strategy described in http://www.jboss.org/community/wiki/EncryptingpasswordsinTeiid The documentation needs to be modified to reflect that. -- 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

13 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-831) Stored procedure execution fails with with out parameters after in

by Steven Hawkins (JIRA)

Stored procedure execution fails with with out parameters after in ------------------------------------------------------------------ Key: TEIID-831 URL: https://jira.jboss.org/jira/browse/TEIID-831 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Stored procedure execution, such as the fakemetadata pm2.sptest8 fail with with out parameters after in. This is due to skipping the index increment for in parameters. -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-715) Allow the user to set null ordering behavior

by Steven Hawkins (JIRA)

Allow the user to set null ordering behavior -------------------------------------------- Key: TEIID-715 URL: https://jira.jboss.org/jira/browse/TEIID-715 Project: Teiid Issue Type: Feature Request Components: Connector API, Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3.0 Sources that support order by may have different null ordering behavior than Teiid (which currently treats null as low). We should support the option for the server to be configured as nulls high, low, always high, or always low. Connectors will need to indicate the sort mode they support so the appropriate push-down and compensating actions can be taken. -- 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

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-765) Procedures without a return parameter and with output parameters indexing issue

by Steven Hawkins (JIRA)

Procedures without a return parameter and with output parameters indexing issue ------------------------------------------------------------------------------- Key: TEIID-765 URL: https://jira.jboss.org/jira/browse/TEIID-765 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Procedures without a return parameter and with output parameters index the output parameter(s) by +1 of what they should be. -- 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

13 years, 9 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