February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-82) subqueries are not supported anywhere other than where and select clauses of querycommands

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-82?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-82: ------------------------------ Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.x > subqueries are not supported anywhere other than where and select clauses of querycommands > ------------------------------------------------------------------------------------------ > > Key: TEIID-82 > URL: https://jira.jboss.org/jira/browse/TEIID-82 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #23760: Subqueries in other place, for example, delete, update, and procedure if statements, and join criteria do not support subqueries in criteria. If this cannot be worked for 5.6, then validations should be added so that invalid subqueries are detected. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-81) Cached plans are too big - can cause out of memory errors

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-81?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-81: ------------------------------ Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Cached plans are too big - can cause out of memory errors > --------------------------------------------------------- > > Key: TEIID-81 > URL: https://jira.jboss.org/jira/browse/TEIID-81 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.x > > > Defect Tracker #12381: Running the coper load tests led to this conclusion: > Each cached plan takes on average 31 KB of memory. > At 140 unique queries / connection and 128 connection this requires over 550 MB of memory just for the plan cache. > Half of the memory was consumed by char[]. Over 10% of the memory was used by ElementSymbol objects. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-78) Need to support SOAP 1.2 in next release across all web service implementations

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-78?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-78: ------------------------------ Component/s: SOAP Services XML Connector Fix Version/s: 6.1.0 Affects Version/s: 6.x > Need to support SOAP 1.2 in next release across all web service implementations > ------------------------------------------------------------------------------- > > Key: TEIID-78 > URL: https://jira.jboss.org/jira/browse/TEIID-78 > Project: Teiid > Issue Type: Bug > Components: SOAP Services, XML Connector > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 6.1.0 > > > Defect Tracker #20946: This will involve changing our implementations over to use the new SOAP fault rules in the 1.2 release as far as i can tell. > We will also need to use the SOAP 1.2 namespaces in our SOAP messages in order to be compliant. > test -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-77) Change dqp to not fully qualify the connector using the VDB and Version

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-77?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-77: ------------------------------ Component/s: Query Engine Affects Version/s: 6.x > Change dqp to not fully qualify the connector using the VDB and Version > ----------------------------------------------------------------------- > > Key: TEIID-77 > URL: https://jira.jboss.org/jira/browse/TEIID-77 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Optional > > Defect Tracker #25044: Issue log as a result of Greg Haber visit. > The connector binding is currently being referenced in the modeler using a fully qualified name that includes the VDB and Version, where on the server is just the name. This causes an issue in the modeler when trying use multi-source bindings. Per Steve H., log this defect. -- 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

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 Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-76?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-76: ------------------------------ Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Attempting to execute a procedure from MM to MM returns error "<procedure>() does not exist" > -------------------------------------------------------------------------------------------- > > Key: TEIID-76 > URL: https://jira.jboss.org/jira/browse/TEIID-76 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.x > > > 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-75) SqlQueryWebService WSDL updates

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-75?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-75: ------------------------------ Component/s: SOAP Services Fix Version/s: 6.1.0 Affects Version/s: 6.x > SqlQueryWebService WSDL updates > ------------------------------- > > Key: TEIID-75 > URL: https://jira.jboss.org/jira/browse/TEIID-75 > Project: Teiid > Issue Type: Bug > Components: SOAP Services > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 6.1.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The WSDL is not WS-I Compliant and it needs to have operations removed per FEDERATE-8. See also tracker defect 25075 -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-74) Move WebServices Resource to System Properties

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-74?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-74: ------------------------------ Component/s: Console Fix Version/s: 6.1.0 Affects Version/s: 6.x > Move WebServices Resource to System Properties > ---------------------------------------------- > > Key: TEIID-74 > URL: https://jira.jboss.org/jira/browse/TEIID-74 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.x > Reporter: Van Halbert > Fix For: 6.1.0 > > > Defect Tracker #19774: See attachment regarding changes. > The properties are misleading and leads to confusion by everyone. > This has been assigned for 4.4, instead of now, because of the moving of properties and it would be better suited to a major version and a migration was required. Therefore, no additional work just to handle the properties would be needed. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-73) Directory validation in XML File connector too optimistic

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-73?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-73: ------------------------------ Component/s: XML Connector Fix Version/s: 6.x Affects Version/s: 6.x > Directory validation in XML File connector too optimistic > --------------------------------------------------------- > > Key: TEIID-73 > URL: https://jira.jboss.org/jira/browse/TEIID-73 > Project: Teiid > Issue Type: Bug > Components: XML Connector > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.x > > > Defect Tracker #18724: When a directory is specified rather than a specific XML file, the directory validation logic has two problems: > 1. it neglects to filter out subdirectories, and > 2. if at least one file validates, it assumes all are good. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-72) show authorization properties on the security summary

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-72?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-72: ------------------------------ Component/s: Console Fix Version/s: 6.1.0 Affects Version/s: 6.x > show authorization properties on the security summary > ----------------------------------------------------- > > Key: TEIID-72 > URL: https://jira.jboss.org/jira/browse/TEIID-72 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.1.0 > > > Defect Tracker #24717: For clarity the authorization properties in system properties should be also be located on the security summary. The should act as dependent properties of the enable authentication and authorization -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-71) Cached code tables not tied to specific vdbs

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-71?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-71: ------------------------------ Component/s: Query Engine Fix Version/s: 6.0.0 Affects Version/s: 6.x > Cached code tables not tied to specific vdbs > -------------------------------------------- > > Key: TEIID-71 > URL: https://jira.jboss.org/jira/browse/TEIID-71 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > See tracker defect 11629 -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009