November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1753) FileStore compaction issues

by Steven Hawkins (JIRA)

FileStore compaction issues --------------------------- Key: TEIID-1753 URL: https://issues.jboss.org/browse/TEIID-1753 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Blocker Fix For: 7.4.1, 7.6 Compaction does not reset the unused space counter, which means that large files will continually be compacted. Also the compaction copy logic does not copy the correct bytes past the first buffer boundary. Finally the batch cleanup logic is not properly coordinated against a simultaneous compaction. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] (TEIID-142) Introduce a mechanism to allow single source updates without an xa txn.

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-142?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-142. -------------------------------- > Introduce a mechanism to allow single source updates without an xa txn. > ----------------------------------------------------------------------- > > Key: TEIID-142 > URL: https://issues.jboss.org/browse/TEIID-142 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.x > Reporter: Steven Hawkins > Priority: Minor > > Defect Tracker #24910: txnAutoWrap = OFF in 5.5 disables the use of local transactions. This was primarily done to support customers who 1. weren't paying for the transactional product > 2. weren't using an XA connection for an update > The concern of 1 goes away in 5.6 as all customers will have a transactional product. The secondary concern requires either a connection property that either ignores autocommit or the generic support of 1 phase commit on connectors supporting update and local transactions. The latter solution would allow non-XA aware connectors to seem XA aware as long as all updates went to a single source. Arjuna would also need to be configured to support the one phase commit optimization. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1812) Client Recieving java.lang.IndexOutOfBoundsException when performing query

by Graeme Gillies (Created) (JIRA)

Client Recieving java.lang.IndexOutOfBoundsException when performing query -------------------------------------------------------------------------- Key: TEIID-1812 URL: https://issues.jboss.org/browse/TEIID-1812 Project: Teiid Issue Type: Bug Affects Versions: 7.5 Environment: java version "1.6.0_20" OpenJDK Runtime Environment (IcedTea6 1.9.8) (rhel-1.22.1.9.8.el5_6-x86_64) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) Running on RHEL 5, teiid inside of JBoss EAP 5.1.1 Client is postgresql command line tool version postgresql-9.1.1-1.fc16.x86_64 Using the command line command psql -h teiid-01.app.eng.bos.redhat.com -p 35432 -U teiid -d EngVDBF Reporter: Graeme Gillies Assignee: Steven Hawkins When attempting to perform the following query using the postgres command line client connecting to teiids postgres emulation layer, we get the following error {code} SELECT components.name, COUNT(bug_id) FROM BugzillaS.bugs bugs, BugzillaS.components components, BugzillaS.profiles profiles WHERE (bugs.component_id = components.id AND bugs.reporter = profiles.userid AND bugs.creation_ts>='2011-10-04') GROUP BY components.name ORDER BY components.name limit 1500; {code} {code} ERROR: java.lang.IndexOutOfBoundsException DETAIL: org.teiid.jdbc.TeiidSQLException: java.lang.IndexOutOfBoundsException {code} Watching the server logs we don't see any such exception reported there, so I'd need some advice on how to get you some more information. Regards, Graeme -- 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

13 years, 10 months

6
11
0 / 0

[JBoss JIRA] (TEIID-1826) RFE/possible optimization: push down parts of some aggregate expressions

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1826?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1826. --------------------------------- > RFE/possible optimization: push down parts of some aggregate expressions > ------------------------------------------------------------------------ > > Key: TEIID-1826 > URL: https://issues.jboss.org/browse/TEIID-1826 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Optional > > suggestion for a potential optimization: It concerns federated queries which do expressions. This is an extremely common requirement in the banking business, the main example being when monetary amounts need to be converted into a reporting currency using a rate in another database. > With the query below, it makes sense that despite the group by, EDS will pull back all the rows so it can multiply one by the other. Unfortunately this is often many millions of records. > Would it be feasible to have an optimization which push-down most of the aggregation to the source, then do a further aggregation in EDS? > * sum the tsl.func_amount, grouped by tsl.currency > * next: get the conversion rates for all the currency codes which have been returned, then sum(total * rate) > Of course, this can only be done for certain kinds of expressions. > select sum(tsl.func_amount * ccy.EuroConversionLegacyRate) > from TSL_FINANCIAL_ACCOUNT_ITEMS_T2 tsl > join t_sdm_currency ccy on tsl.currency = ccy.currencycode > where tsl.business_date = '2011-06-29' > group by ccy.EuroConversionLegacyRate -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1781) It is possible to call stored procedure via Teiid JDBC driver on VDB even though VDB doesn't contain the imported procedure

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1781?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1781. --------------------------------- > It is possible to call stored procedure via Teiid JDBC driver on VDB even though VDB doesn't contain the imported procedure > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1781 > URL: https://issues.jboss.org/browse/TEIID-1781 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.4.1 > Reporter: Filip Nguyen > Assignee: Van Halbert > > I use setting same as in SOA-3478. But I deleted the procedure from xmi files in the VDB (attachment) and changed query to: > {code:title=Teiid Query|borderStyle=solid} > String query = "{ CALL getEmployeeSurnames }"; > {code} > The Query is called and result set is returned. > After conversation with Steven Hawkins I understand that this shouldn't be possible and Teiid should respond that it cannot resolve the query. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-554) searchability metadata should be type based

by Steven Hawkins (JIRA)

searchability metadata should be type based ------------------------------------------- Key: TEIID-554 URL: https://jira.jboss.org/jira/browse/TEIID-554 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.x Since searchability metadata is element based our check for (CapabilitiesUtil) gathers all elements in the expression - regardless of the type of the whole expression. This may be quite difficult to make this change in the existing metadata framework. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] (TEIID-999) Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-999?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-999: --------------------------------- Parent: TEIID-965 Issue Type: Sub-task (was: Feature Request) > Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors > --------------------------------------------------------------------------------- > > Key: TEIID-999 > URL: https://issues.jboss.org/browse/TEIID-999 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Environment: MS Excel 2003 > Reporter: Larry O'Leary > Fix For: Open To Community > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Create a capabilities set that can be used by the MS Access and MS Excel connectors. We currently offer the MS Excel connector which is using the generic JDBC capabilities and translators and the MS Access connector which is using its own capabilities and translators but they do not reflect MS Access. > The replacement connector types should work very much like the current ones but reflect the base capabilities offered by MS JET 4 and specific capabilities as defined by the MS Excel and MS Access limitations to the MS JET 4 implementation. At bare minimum we should support push-down of all currently defined capabilities and remove any current ones that are not valid for MS JET/MS Access/MS Excel. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1070) Create Amazon SimpleDB Connector

by John Doyle (JIRA)

Create Amazon SimpleDB Connector --------------------------------- Key: TEIID-1070 URL: https://jira.jboss.org/jira/browse/TEIID-1070 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Reporter: John Doyle Assignee: John Doyle Fix For: 7.1 We need connectivity to Amazon SimpleDB. This should be accomplished through a dedicated connector. Simple DB presents a few challenges as a Teiid source as it is more like a spreadsheet than a database. Simple DB "Domains' are like individual worksheets and contain any number of items. Items however can have any number of attributes, and the attributes do not have to be the same for ever item. So in a single Domain you can have an item with the attributes Size and Color, and another item with the attributes Color and ExpirationDate. This presents both modeling issues and SQL execution issues. None of them are insurmountable, but users will have to understand the issues and design their integration around them. -- 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, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIID-1757) Add Support for OData Data Sources

by Ted Jones (JIRA)

Add Support for OData Data Sources ---------------------------------- Key: TEIID-1757 URL: https://issues.jboss.org/browse/TEIID-1757 Project: Teiid Issue Type: Feature Request Reporter: Ted Jones Assignee: Steven Hawkins OData data sources, like SAP Gateway, should be consumable by Teiid. I suggest either a new translator or extending the existing web service translator to enable the OData protocol. A new translator would be cleaner, but since OData uses REST, it may not make sense to to have another translator. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1311) Consider developing a connector/translator to Cassandra/Thrift

by Ken Johnson (JIRA)

Consider developing a connector/translator to Cassandra/Thrift -------------------------------------------------------------- Key: TEIID-1311 URL: https://jira.jboss.org/browse/TEIID-1311 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 7.1 Environment: Any Reporter: Ken Johnson Assignee: Steven Hawkins Priority: Minor Apache Cassandra is starting to see uptake beyond the big name social network players. Has any thought been given to offering connectivity to Cassandra through Teiid? Perhaps this is through consuming the Thrift file as metadata source. -- 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

13 years, 10 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2011