May 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-832) Support calling oracle stored functions returning result sets as stored procedures

by Steven Hawkins (JIRA)

Support calling oracle stored functions returning result sets as stored procedures ---------------------------------------------------------------------------------- Key: TEIID-832 URL: https://jira.jboss.org/jira/browse/TEIID-832 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3.0 This is only an issue with oracle native drivers, which need to have the returned result set explicitly called as a return parameter. For this to work we'll need to ensure that the import metadata on a procedure is being set to isFunction appropriately and then use that metadata in the Oracle connector. -- 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, 6 months

5
7
0 / 0

[JBoss JIRA] Created: (TEIID-1518) Add a correlated subquery evaluation cache

by Steven Hawkins (JIRA)

Add a correlated subquery evaluation cache ------------------------------------------ Key: TEIID-1518 URL: https://issues.jboss.org/browse/TEIID-1518 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins The subquery aware evaluator should cache deterministic evaluations for reuse. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-1563) Refresh a Materialized View without parameters from admin console

by Stephen Brooks (JIRA)

Refresh a Materialized View without parameters from admin console ----------------------------------------------------------------- Key: TEIID-1563 URL: https://issues.jboss.org/browse/TEIID-1563 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1.1 Environment: EDS on RHEL 5, Admin Console with Firefox 4.0 Reporter: Stephen Brooks Assignee: Steven Hawkins Priority: Minor Found an EDS bug in the admin console where it tries to refresh without parameters. Steps to reproduce: 1. Go to the 'Control' tab for a VDB 2. Click 'Refresh a Materialized View' 3. Don't enter information, just click 'Cancel' 4. Click 'Refresh a Materialized View' again -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

5
6
0 / 0

[JBoss JIRA] Created: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval

by Graeme Gillies (JIRA)

Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval --------------------------------------------------------------------------------------------------------------------- Key: TEIID-1596 URL: https://issues.jboss.org/browse/TEIID-1596 Project: Teiid Issue Type: Feature Request Reporter: Graeme Gillies Assignee: Steven Hawkins In the teiid documentation there is no mention (from what I can find) of exactly what the option queryThresholdInSecs does. The xml file states "Long running query threshold, after which a alert can be generated by tooling if configured", what tooling is this exactly? Does it alert and stop the query, or just alert? On the same token, there is the configuration item maxSourceRows which is configured per instance. Unfortunately this isn't flexible enough sometimes, and it would be better if this option could be configured per VDB and per data role as well (some people can get more data than others). I would expect the determination of what maxSourceRows is for a query should be as follows 1) If maxSourceRows is set for the data role the user has, use that (in the case of two data roles with different values, use the largest value) 2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use that value 3) If maxSourceRows is not set on the vdb or any data roles the user has, use the instance setting. Likewise, the setting maxSourceRows should not only be configurable per data role, vdb, instance, but also the setting queryThresholdInSecs, and either that option or another option should be put in place that allows us to hard limit the length of time a query can run. This is because in teiid we want to be able to say users cannot write a big huge query that will take more than X amount of seconds to execute, to stop someone in teiid giving it a huge query and hammering all the backend databases. Configuring this option by vdb and data role (as some people are more trusted and can run longer queries) would be fantastic. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
9
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-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-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 May 2011