October 2011 - teiid-issues - Jboss List Archives

[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] (TEIID-1793) Receive " User <user@teiid-security> is not entitled to action <READ> for 1 or more of the groups/elements/procedures." error on unqualified SQL if data roles are active

by Paul Nittel (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1793?page=com.atlassian.jira.plugin... ] Paul Nittel closed TEIID-1793. ------------------------------ Tested and closed. > Receive " User <user@teiid-security> is not entitled to action <READ> for 1 or more of the groups/elements/procedures." error on unqualified SQL if data roles are active > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1793 > URL: https://issues.jboss.org/browse/TEIID-1793 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.6 > > > If you run a query 'SELECT * FROM MyProc' i.e. without a model/schema name, You'll receive the below error if an all Access Data Role is assigned to the VDB. If you remove the Data Role, the query succeeds. > Error: Remote org.teiid.api.exception.query.QueryValidatorException: User <user@teiid-security> is not entitled to action <READ> for 1 or more of the groups/elements/procedures. > SQLState: 50000 > ErrorCode: 0 > The query only succeeds if you fully qualify the proc/table when Data Roles are used. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1794) Teiid Plugin shows zero for all metrics except Session Count

by Paul Nittel (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1794?page=com.atlassian.jira.plugin... ] Paul Nittel closed TEIID-1794. ------------------------------ Tested and closed. > Teiid Plugin shows zero for all metrics except Session Count > ------------------------------------------------------------ > > Key: TEIID-1794 > URL: https://issues.jboss.org/browse/TEIID-1794 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Ted Jones > Priority: Critical > > Using either JON or the Admin Console no metrics appear to be collected for Data Services except Session count. All measurements are enable and set to collect every 10 minutes, but nothing happens. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-964) Must pushdown functions in select clause

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-964?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-964. ---------------------------------- Assignee: Steven Hawkins Resolution: Done Added support for pushing must pushdown functions in the select clause. The logic could be expended later into more general projection/subexpression pushing that works on all clauses. > Must pushdown functions in select clause > ---------------------------------------- > > Key: TEIID-964 > URL: https://issues.jboss.org/browse/TEIID-964 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.6 > > > (F_ATM_REPORT_TYPE is a DB function) > SELECT F_ATM_REPORT_TYPE (BUS_LINE_CODE) FROM ... > Will not have the function pushed down if it only appears in the select clause. The planner must check if a function is pushdown only when it appears in the select clause and determine a source to push it to. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-964) Must pushdown functions in select clause

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-964?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-964: --------------------------------- Fix Version/s: 7.6 (was: 9.0) Affects Version/s: 6.0.0 > Must pushdown functions in select clause > ---------------------------------------- > > Key: TEIID-964 > URL: https://issues.jboss.org/browse/TEIID-964 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 7.6 > > > (F_ATM_REPORT_TYPE is a DB function) > SELECT F_ATM_REPORT_TYPE (BUS_LINE_CODE) FROM ... > Will not have the function pushed down if it only appears in the select clause. The planner must check if a function is pushdown only when it appears in the select clause and determine a source to push it to. -- 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

12 years, 8 months

1
0
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 October 2011