June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (TEIID-36) XAConnection needs to notify when it is no longer valid

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-36?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins resolved TEIID-36. -------------------------------- Resolution: Done added to the proxy logic to call to the connection listener when the connection is invalid (invalidsessionexception or a communicationexception) > XAConnection needs to notify when it is no longer valid > ------------------------------------------------------- > > Key: TEIID-36 > URL: https://jira.jboss.org/browse/TEIID-36 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.0 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The XAConnection does not properly notify listeners when the connection has become invalid. -- 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] Updated: (TEIID-36) XAConnection needs to notify when it is no longer valid

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-36?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins updated TEIID-36: ------------------------------- Summary: XAConnection needs to notify when it is no longer valid (was: MMXADataSource needs to notify when it is no longer valid) Fix Version/s: 7.0 (was: 8.x) Affects Version/s: 7.0 (was: 8.x) Description: The XAConnection does not properly notify listeners when the connection has become invalid. (was: The MMXADataSource does not properly notify listeners when the connection has become invalid.) Moving up to 7.0 since some pools will not have query tests on by default and will look for notifications for invalidation. > XAConnection needs to notify when it is no longer valid > ------------------------------------------------------- > > Key: TEIID-36 > URL: https://jira.jboss.org/browse/TEIID-36 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.0 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The XAConnection does not properly notify listeners when the connection has become invalid. -- 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] Commented: (TEIID-231) Ability to support Connector Level UDF functions in the System

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-231?page=com.atlassian.jira.plugin.sy... ] Ramesh Reddy commented on TEIID-231: ------------------------------------ Now that we have VDB scoped Function Definitions and Translators from 7.0, does it make sense to add the definition of new function to the "translator" fragment in the "vdb.xml" file? > Ability to support Connector Level UDF functions in the System > -------------------------------------------------------------- > > Key: TEIID-231 > URL: https://jira.jboss.org/browse/TEIID-231 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 7.1 > > > Currently we have UDF and Connector capabilities to define some custom functions in supported by a connector, however this is not seem less to deploy along with the connector, as connector functions do not support any parameters or design tools to define/declare them in CDK. We need a way to define and develop functions supported by a connector. > Suggestions. > 1) Use designer to define capabilities in a XMI file and attach with the connector, and let the server or MMQuery load these XMI files dynamically into the engine. > 2) -- 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] Updated: (TEIID-167) Enhancement: Connector Developer's Kit needs overhaul

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-167?page=com.atlassian.jira.plugin.sy... ] Ramesh Reddy updated TEIID-167: ------------------------------- Assignee: (was: John Doyle) > Enhancement: Connector Developer's Kit needs overhaul > ----------------------------------------------------- > > Key: TEIID-167 > URL: https://jira.jboss.org/browse/TEIID-167 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Documentation > Affects Versions: 7.0 > Reporter: Ramesh Reddy > Fix For: 7.1 > > > Defect Tracker #24469: The CDK kit is based on the Command Shell framework, this needs to be moved to either MMSehll based or the Beanshell based framework, with better help system -- 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] Commented: (TEIID-167) Enhancement: Connector Developer's Kit needs overhaul

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-167?page=com.atlassian.jira.plugin.sy... ] Ramesh Reddy commented on TEIID-167: ------------------------------------ With Translator development simplified to extending one class, and after removing any special packaging needs and connector types not sure what advantage this feature provides. User can use any Java development environment and accomplish the task with instructions. The one feature missing is sandbox testing environment, with current architecture this is not possible yet. Once "embedded" Teiid is available this can be done. Is this something we still want to pursue? > Enhancement: Connector Developer's Kit needs overhaul > ----------------------------------------------------- > > Key: TEIID-167 > URL: https://jira.jboss.org/browse/TEIID-167 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Documentation > Affects Versions: 7.0 > Reporter: Ramesh Reddy > Assignee: John Doyle > Fix For: 7.1 > > > Defect Tracker #24469: The CDK kit is based on the Command Shell framework, this needs to be moved to either MMSehll based or the Beanshell based framework, with better help system -- 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] Updated: (TEIID-99) Stored procedures should work in multisource connector binding scenarios

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-99?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins updated TEIID-99: ------------------------------- Fix Version/s: 8.0 (was: 7.1) Affects Version/s: 6.0.0 (was: 8.x) pushing to 8 > Stored procedures should work in multisource connector binding scenarios > ------------------------------------------------------------------------ > > Key: TEIID-99 > URL: https://jira.jboss.org/browse/TEIID-99 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.0 > > > Defect Tracker #24614: Stored procedures should work in multisource connector binding scenarios by adding another input parameter named SOURCE_NAME -- 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] Updated: (TEIID-76) Attempting to execute a procedure from MM to MM returns error "<procedure>() does not exist"

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-76?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins updated TEIID-76: ------------------------------- Fix Version/s: 7.1 (was: 8.x) Affects Version/s: 6.0.0 (was: 8.x) > Attempting to execute a procedure from MM to MM returns error "<procedure>() does not exist" > -------------------------------------------------------------------------------------------- > > Key: TEIID-76 > URL: https://jira.jboss.org/browse/TEIID-76 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.1 > > > Defect Tracker #24378: I have a VDB which executes a virtual procedure that resides on another MMServer in another VDB. I have verified that I am able to execute the procedure when connected from a client app to the 2nd VDB but when I attempt to execute the same procedure from the 1st VDB I receive the following error: > Error: com.metamatrix.jdbc.MMSQLException: Error trying to execute a query statement { call "ApplicationMetaData.Mapping.Template.Insert"(?,?,?,?,?,?,?,?,?,?)}: "ApplicationMetaData.Mapping.Template.Insert" does not exist., SQL State: 38000, Error Code: 0 > Here is the exception that appears in the MM_Mappings MMXServer: > com.metamatrix.data.exception.ConnectorException[0]: java.sql.SQLException: Error trying to execute a query statement { call "ApplicationMetaData.Mapping.Template.Insert"(?,?,?,?,?,?,?,?,?,?)}: "ApplicationMetaData.Mapping.Template.Insert" does not exist. > at com.metamatrix.common.util.exception.SQLExceptionUnroller.unRollException(SQLExceptionUnroller.java:43) > at com.metamatrix.connector.jdbc.JDBCProcedureExecution.execute(JDBCProcedureExecution.java:77) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:241) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processBatchRequest(ConnectorWorker.java:166) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processRequest(ConnectorWorker.java:150) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:135) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:51) -- 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] Assigned: (TEIID-76) Attempting to execute a procedure from MM to MM returns error "<procedure>() does not exist"

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-76?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins reassigned TEIID-76: ---------------------------------- Assignee: Steve Hawkins > Attempting to execute a procedure from MM to MM returns error "<procedure>() does not exist" > -------------------------------------------------------------------------------------------- > > Key: TEIID-76 > URL: https://jira.jboss.org/browse/TEIID-76 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steve Hawkins > Priority: Optional > Fix For: 7.1 > > > Defect Tracker #24378: I have a VDB which executes a virtual procedure that resides on another MMServer in another VDB. I have verified that I am able to execute the procedure when connected from a client app to the 2nd VDB but when I attempt to execute the same procedure from the 1st VDB I receive the following error: > Error: com.metamatrix.jdbc.MMSQLException: Error trying to execute a query statement { call "ApplicationMetaData.Mapping.Template.Insert"(?,?,?,?,?,?,?,?,?,?)}: "ApplicationMetaData.Mapping.Template.Insert" does not exist., SQL State: 38000, Error Code: 0 > Here is the exception that appears in the MM_Mappings MMXServer: > com.metamatrix.data.exception.ConnectorException[0]: java.sql.SQLException: Error trying to execute a query statement { call "ApplicationMetaData.Mapping.Template.Insert"(?,?,?,?,?,?,?,?,?,?)}: "ApplicationMetaData.Mapping.Template.Insert" does not exist. > at com.metamatrix.common.util.exception.SQLExceptionUnroller.unRollException(SQLExceptionUnroller.java:43) > at com.metamatrix.connector.jdbc.JDBCProcedureExecution.execute(JDBCProcedureExecution.java:77) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:241) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processBatchRequest(ConnectorWorker.java:166) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processRequest(ConnectorWorker.java:150) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:135) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:51) -- 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] Resolved: (TEIID-76) Attempting to execute a procedure from MM to MM returns error "<procedure>() does not exist"

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-76?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins resolved TEIID-76. -------------------------------- Resolution: Done added logic to allow the procedure to be vdb or catalog qualified. > Attempting to execute a procedure from MM to MM returns error "<procedure>() does not exist" > -------------------------------------------------------------------------------------------- > > Key: TEIID-76 > URL: https://jira.jboss.org/browse/TEIID-76 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.1 > > > Defect Tracker #24378: I have a VDB which executes a virtual procedure that resides on another MMServer in another VDB. I have verified that I am able to execute the procedure when connected from a client app to the 2nd VDB but when I attempt to execute the same procedure from the 1st VDB I receive the following error: > Error: com.metamatrix.jdbc.MMSQLException: Error trying to execute a query statement { call "ApplicationMetaData.Mapping.Template.Insert"(?,?,?,?,?,?,?,?,?,?)}: "ApplicationMetaData.Mapping.Template.Insert" does not exist., SQL State: 38000, Error Code: 0 > Here is the exception that appears in the MM_Mappings MMXServer: > com.metamatrix.data.exception.ConnectorException[0]: java.sql.SQLException: Error trying to execute a query statement { call "ApplicationMetaData.Mapping.Template.Insert"(?,?,?,?,?,?,?,?,?,?)}: "ApplicationMetaData.Mapping.Template.Insert" does not exist. > at com.metamatrix.common.util.exception.SQLExceptionUnroller.unRollException(SQLExceptionUnroller.java:43) > at com.metamatrix.connector.jdbc.JDBCProcedureExecution.execute(JDBCProcedureExecution.java:77) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:241) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processBatchRequest(ConnectorWorker.java:166) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processRequest(ConnectorWorker.java:150) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:135) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:51) -- 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] Resolved: (TEIID-968) Timestamp literals with fractional seconds result in source query execution performance when being compared to less percise time types

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-968?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins resolved TEIID-968. --------------------------------- Assignee: Steve Hawkins (was: Larry O'Leary) Fix Version/s: 7.1 Resolution: Done The JDBC translator now defaults to preparedstatements, so hopefully this shouldn't be much of an issue. Modified the translation of a timestamp literal to use the to_date function if the nanoseconds are 0. > Timestamp literals with fractional seconds result in source query execution performance when being compared to less percise time types > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-968 > URL: https://jira.jboss.org/browse/TEIID-968 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 7.1 > Environment: MM 5.5.3 > Oracle 10i > Oracle ANSI Connector > Reporter: Larry O'Leary > Assignee: Steve Hawkins > Fix For: 7.1 > > Attachments: mylyn-context.zip > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Seeing that the only "time" type for MetaMatrix is timestamp and Oracle uses DATE to store time and TIMESTAMP to store time with fractional seconds we need a method of sending a timestamp as a literal that Oracle can use as a DATE instead of requiring the comparison to be normalized to TIMESTAMP as this results in a huge performance hit within Oracle. > It is possible to change this behaviour by actually setting a date only column to MetaMatrix date in the model but this does not account for situations where a DATE column in Oracle holds date and time information. In those cases, I would still need to use timestamp for MetaMatrix and this would result in a huge performance impact. > Oracle will automatically use the widest type possible when doing comparisons so if I store date only data in a DATE column and then attempt to query using criteria on that column such ad {d'2000-01-01'} the date literal gets converted to {ts'2000-01-01 00:00:00.0'} prior to it being sent to Oracle. This will result in Oracle converting my DATE column into a TIMESTAMP column to handle the comparison. > The current DataDirect driver we are using actually accounts for this issue when dealing with timestamp literals. Basically, if the timestamp literal does not include fractional seconds, the driver will pass it to Oracle as a date instead of a timestamp. This greatly improves performance in these situations. > So, if the current logic is kept, but we simply truncate the timestamp literal to remove the fractional seconds, we get the advantage of the driver performing better type mapping in this situation. -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010