November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1835) Querying a table built from WSDL Importer has no source query?

by Paul Nittel (Created) (JIRA)

Querying a table built from WSDL Importer has no source query? -------------------------------------------------------------- Key: TEIID-1835 URL: https://issues.jboss.org/browse/TEIID-1835 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4.1 Environment: SOA-P 5.2 GA Reporter: Paul Nittel Assignee: Steven Hawkins I had previously deployed a Web service and figured I'd import the WSDL to make a relational model. The Designer process went well. The create procedure, called by: exec PartsWebXML.getSuppInfo.create_SuppInfo_Input('S106') generates a result <SuppInfo_Input xmlns="http://www.metamatrix.com/SuppInfo_Input"><SUPPLIER_ID>S106</SUPPLIER_ID></SuppInfo_Input> which goes into my query: exec PartsWebXML.getSuppInfo.extract_SuppInfo_output_Instance('<SuppInfo_Input xmlns="http://www.metamatrix.com/SuppInfo_Input"><SUPPLIER_ID>S106</SUPPLIER_ID></SuppInfo_Input>') The result set consists of zeros rows (only column headings). The query plan (attached) seems to be lacking a source query. The command log entries (also attached) support that theory, AFAICT. I'm also attaching the Model Project Set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (TEIID-1797) When a message (i.e., WARN) is logged and its associated with a translator/connector, it would be nice to know to which one it applied

by Van Halbert (Created) (JIRA)

When a message (i.e., WARN) is logged and its associated with a translator/connector, it would be nice to know to which one it applied -------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1797 URL: https://issues.jboss.org/browse/TEIID-1797 Project: Teiid Issue Type: Enhancement Components: LDAP Connector Affects Versions: 7.5 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor Seeing the following warning when running a query: WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue50) Search results exceeded size limit. Results may be incomplete There are 2 sources (jdbc and ldap) in the vdb, and not sure which one is causing the issue. Also, seeing this warning, I'm thinking I may not have all my results. What do I do or change in order to get all the results? Not sure what to do. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (TEIID-1796) Source Functions being pushed to the source are not taking into account NameInSource

by Paul Nittel (Created) (JIRA)

Source Functions being pushed to the source are not taking into account NameInSource ------------------------------------------------------------------------------------ Key: TEIID-1796 URL: https://issues.jboss.org/browse/TEIID-1796 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: PushDownTest_MPS.zip I imported BQT from Oracle, but did not import the SQUIRREL_GET_ERROR_OFFSET function. I then used the Source Function wizard to create the function. I named it RallySQUIRREL_GET_ERROR_OFFSET. When I executed the query, the function RallySQUIRREL_GET_ERROR_OFFSET was not found by Oracle. I had to rename the source function model to match the name of the function in Oracle. Shouldn't have to do that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
4
0 / 0

[JBoss JIRA] (TEIID-1802) Async Event Processing: Translator callback indicating data is available

by Mark Addleman (Created) (JIRA)

Async Event Processing: Translator callback indicating data is available ------------------------------------------------------------------------- Key: TEIID-1802 URL: https://issues.jboss.org/browse/TEIID-1802 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins In order to support more efficient streams of asynchronous events, the Execution Context should provide a callback from the translator to the engine to indicate that data is available. This semantics of this callback are analogous to the DataNotAvailableException. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (TEIID-1768) Temp table becomes unusable by other threads

by Steven Hawkins (Created) (JIRA)

Temp table becomes unusable by other threads -------------------------------------------- Key: TEIID-1768 URL: https://issues.jboss.org/browse/TEIID-1768 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 7.4.1, 7.6 If an update fails, the atomic rollback processing fails to properly unlock the write lock. Any other subsequent thread accessing the table would be locked out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] (TEIID-1800) Async Event Processing: Standardize JDBC Callback API

by Mark Addleman (Created) (JIRA)

Async Event Processing: Standardize JDBC Callback API ----------------------------------------------------- Key: TEIID-1800 URL: https://issues.jboss.org/browse/TEIID-1800 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins The existing callback API used by ODBC should be standardized and made friendly for async event processing. Basicaly, an interface that specifies three methods should suffice: public void onResult(ResultSet rs); public void onComplete(); public void onException(Exception e); Should address the specific semantics of the result set returned in the onResult() method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
4
0 / 0

[JBoss JIRA] Created: (TEIID-1750) Memory handling improvements

by Steven Hawkins (JIRA)

Memory handling improvements ---------------------------- Key: TEIID-1750 URL: https://issues.jboss.org/browse/TEIID-1750 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 The buffermanager will create softreferences for batches that prefer memory, but does not track the memory as held once the value has been passivated. Also small lobs, such as xml values created via sqlxml, should be inlined into results for greater performance - and so that they can be paged out by the buffermanager rather than being held by a lobmanager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
6
0 / 0

[JBoss JIRA] (TEIID-1787) Prepared batch failure

by Steven Hawkins (Created) (JIRA)

Prepared batch failure ---------------------- Key: TEIID-1787 URL: https://issues.jboss.org/browse/TEIID-1787 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins If a prepared batch of atomic queries is performed against a source that does not support support batching, then an NPE will be thrown by the batching logic. An example of this scenario would be batching against a temp table using simple insert statements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] (TEIID-1810) Add Hive Translator that support HDFS

by Ramesh Reddy (Created) (JIRA)

Add Hive Translator that support HDFS ------------------------------------- Key: TEIID-1810 URL: https://issues.jboss.org/browse/TEIID-1810 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Reporter: Ramesh Reddy Hive provides SQL interface to data that is stored inside the Hadoop based data store. Build a Teiid translator for Hive interface to access the data in the Hadoop. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-1675) Add capability to insert/update/delete multi-value attributes in LDAP connector

by Marc Shirley (JIRA)

Add capability to insert/update/delete multi-value attributes in LDAP connector ------------------------------------------------------------------------------- Key: TEIID-1675 URL: https://issues.jboss.org/browse/TEIID-1675 Project: Teiid Issue Type: Feature Request Components: LDAP Connector Affects Versions: 7.4 Reporter: Marc Shirley Assignee: Steven Hawkins Add ability to insert/update/delete multi-value attributes through the LDAP connector. For example, this would present the opportunity for maintaining group membership through modifying the list of member attribute values in an LDAP groupOfNames object. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2011