September 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1762) Exception when using Teiid with BIRT Report Designer

by Graeme Gillies (JIRA)

Exception when using Teiid with BIRT Report Designer ---------------------------------------------------- Key: TEIID-1762 URL: https://issues.jboss.org/browse/TEIID-1762 Project: Teiid Issue Type: Bug Affects Versions: 7.5 Environment: java-1.6.0-openjdk-1.6.0.0-59.1.10.3.fc15.i686 java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.3) (fedora-59.1.10.3.fc15-i386) OpenJDK Server VM (build 20.0-b11, mixed mode) On Fedora 15 Eclipse version Helios, using Birt version 3.7 milestone. Connecting to teiid 7.5 (in JBoss EAP 5.1.1) running on RHEL 5 Reporter: Graeme Gillies Assignee: Steven Hawkins Hi, I've been trying to use the Birt report Designer tool in eclipse to talk to teiid in order to look at designing some reports on top of it. I can add the datasource fine but when I go to create a data set, I notice the following error getting spammed to the eclipse log {code} Sep 26, 2011 12:00:39 PM org.eclipse.birt.report.data.oda.jdbc.ui.model.SchemaNode refetchChildren WARNING: Column name "TABLE_NAME" does not exist. org.teiid.jdbc.TeiidSQLException: Column name "TABLE_NAME" does not exist. at org.teiid.jdbc.ResultSetImpl.findColumnIndex(ResultSetImpl.java:1227) at org.teiid.jdbc.ResultSetImpl.findColumn(ResultSetImpl.java:1214) at org.teiid.jdbc.ResultSetImpl.getString(ResultSetImpl.java:826) at org.eclipse.birt.report.data.oda.jdbc.ui.model.SchemaNode.refetchChildren(SchemaNode.java:71) at org.eclipse.birt.report.data.oda.jdbc.ui.model.RootNode.refetchChildren(RootNode.java:106) at org.eclipse.birt.report.data.oda.jdbc.ui.model.ChildrenAllowedNode$1TempThread.run(ChildrenAllowedNode.java:35) Sep 26, 2011 12:00:54 PM org.eclipse.birt.report.data.oda.jdbc.ui.model.SchemaNode refetchChildren WARNING: Column name "TABLE_NAME" does not exist. org.teiid.jdbc.TeiidSQLException: Column name "TABLE_NAME" does not exist. at org.teiid.jdbc.ResultSetImpl.findColumnIndex(ResultSetImpl.java:1227) at org.teiid.jdbc.ResultSetImpl.findColumn(ResultSetImpl.java:1214) at org.teiid.jdbc.ResultSetImpl.getString(ResultSetImpl.java:826) at org.eclipse.birt.report.data.oda.jdbc.ui.model.SchemaNode.refetchChildren(SchemaNode.java:71) at org.eclipse.birt.report.data.oda.jdbc.ui.model.RootNode.refetchChildren(RootNode.java:106) at org.eclipse.birt.report.data.oda.jdbc.ui.model.ChildrenAllowedNode$1TempThread.run(ChildrenAllowedNode.java:35) {code} We have also noticed the problem when using other reporting engines like http://datavision.sourceforge.net/ which throw the same error. Is it possible to have the column added to whatever table is needed (I assume the SYS model) in order for these errors to not occur? Thanks, Graeem -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
6
0 / 0

[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

12 years, 7 months

3
3
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

12 years, 7 months

2
1
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

12 years, 7 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

12 years, 7 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

12 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1741) Record level audit trail in teiid log files

by Monika Ahuja (JIRA)

Record level audit trail in teiid log files ------------------------------------------- Key: TEIID-1741 URL: https://issues.jboss.org/browse/TEIID-1741 Project: Teiid Issue Type: Feature Request Reporter: Monika Ahuja Assignee: Steven Hawkins In order to track the audit trail for patient identified information access, we would like to track the executed queries, results as well as the timestamps for each user's query and its result. Essentially we need a report providing the list of Medical Record Numbers accessed by each user id and I think we can use the Logs to track that (unless you suggest a better way). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-511) Make process plans serizializable.

by Steven Hawkins (JIRA)

Make process plans serizializable. ---------------------------------- Key: TEIID-511 URL: https://jira.jboss.org/jira/browse/TEIID-511 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.x Processing plans should be serializable to take advantage of replication and non-memory caches. See also TEIID-81 -- 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

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIID-1589) metadata per translator per request

by Mark Addleman (JIRA)

metadata per translator per request ----------------------------------- Key: TEIID-1589 URL: https://issues.jboss.org/browse/TEIID-1589 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins Priority: Minor I'd like to the translator to attach metadata to the results it passes back to the Teiid JDBC client. For example, I'd like the translator to examine the connection object and decorate the returned data with which datasource provided the data. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

6
9
0 / 0

[JBoss JIRA] Created: (TEIID-1607) Provide a data role injection point where a different implementation could be used for role validation

by Van Halbert (JIRA)

Provide a data role injection point where a different implementation could be used for role validation ------------------------------------------------------------------------------------------------------ Key: TEIID-1607 URL: https://issues.jboss.org/browse/TEIID-1607 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.4.1 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Blocker Provide a data role injection point where a different implementation could be used for role validation. This interface would provide full control of the validation, instead of receiving parts of the sql to validate. As per our meeting, Steve can probably describe this feature better and talk to the true requirement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2011