February 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3911) Nearly all odata4 errors reported as internal server errors

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3911?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3911: ------------------------------------- This is worked under upstream as https://issues.apache.org/jira/browse/OLINGO-874 > Nearly all odata4 errors reported as internal server errors > ----------------------------------------------------------- > > Key: TEIID-3911 > URL: https://issues.jboss.org/browse/TEIID-3911 > Project: Teiid > Issue Type: Sub-task > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Fix For: 9.0 > > > From the TeiidServiceHandler we generally rethrow our exceptions as ODataApplicationExceptions that have a status code of 500 - however even using a different status code still results in a 500 error as the Olingo framework expects exception subclasses to be used (see ErrorHandler.handleException - a general application exception is always a 500 error). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3911) Nearly all odata4 errors reported as internal server errors

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3911?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3911: -------------------------------- Parent: TEIID-3932 Issue Type: Sub-task (was: Quality Risk) > Nearly all odata4 errors reported as internal server errors > ----------------------------------------------------------- > > Key: TEIID-3911 > URL: https://issues.jboss.org/browse/TEIID-3911 > Project: Teiid > Issue Type: Sub-task > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Fix For: 9.0 > > > From the TeiidServiceHandler we generally rethrow our exceptions as ODataApplicationExceptions that have a status code of 500 - however even using a different status code still results in a 500 error as the Olingo framework expects exception subclasses to be used (see ErrorHandler.handleException - a general application exception is always a 500 error). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2403) SAML support in Teiid based web services

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2403?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2403. --------------------------------- Fix Version/s: 8.12.5 Assignee: Ramesh Reddy Resolution: Done See document at https://docs.jboss.org/author/display/teiid812final/SAML+based+security+f... > SAML support in Teiid based web services > ---------------------------------------- > > Key: TEIID-2403 > URL: https://issues.jboss.org/browse/TEIID-2403 > Project: Teiid > Issue Type: Feature Request > Components: Server, SOAP Services > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12.5 > > > Currently there is no built in support for SAML based authentication for OData based REST Services and also REST based WAR created automatically. They should provide an option to support SAML. > Designer based web services (REST, SOAP) are not part of this JIRA, they should be handled using a separate TEIIDDES JIRA. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3035) Request to add NTLM Security to Web service datasources

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3035?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3035: ----------------------------------- Assignee: Ramesh Reddy > Request to add NTLM Security to Web service datasources > ------------------------------------------------------- > > Key: TEIID-3035 > URL: https://issues.jboss.org/browse/TEIID-3035 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > > Currently the only Security types we support for Web Service data sources is None, HTTPBasic and WSSecurity can NTLM be added? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3980) NPE with Salesforce retrieve query and no matching entity

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3980: ------------------------------------- Summary: NPE with Salesforce retrieve query and no matching entity Key: TEIID-3980 URL: https://issues.jboss.org/browse/TEIID-3980 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 8.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0, 8.12.5, 8.13.2 A query such as: select name, id from BusinessProcess where id = <does not exist> will result in an NPE since the retrieve call returns a null record for each id that doesn't match. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3255) Support PicketBox / XACML authorization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3255?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3255: ------------------------------------- PicketLink/PicketBox are defunct projects now, Keycloak is new direction. I think we need to rebase this on the new framework. > Support PicketBox / XACML authorization > --------------------------------------- > > Key: TEIID-3255 > URL: https://issues.jboss.org/browse/TEIID-3255 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.9 > Reporter: John Muller > Fix For: Open To Community > > > We would like the OData, OData4, JDBC, and ODBC transports of Teiid to act as an XACML policy enforcement point for all CRUD operations (as well as execute stored procedures). Looking through old JIRAs: > https://issues.jboss.org/browse/TEIID-1031 > it looks like this was considered back in the mid-2010 timeframe, but wasn't fully thought through. With XACML 3.0, it's possible to use Multiple Decision Profile to get all policy decisions for a given user / resource (or just everything for a user for multiple resources). Our idea here is to have Teiid set the action to be one of (SELECT|INSERT|UPDATE|DELETE|CREATE|DROP|EXECUTE) and the resource to be the fully qualified table (vdbName, SchemaName, TableName) plus a map of projected columns by the query. While this doesn't solve row-based restrictions, it would solve column / object based restrictions. MDP could be used to get policy decisions for all objects under a given schema. > Thoughts? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3321) Support Adabas as a data source

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3321?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3321: ----------------------------------- Assignee: (was: Steven Hawkins) > Support Adabas as a data source > ------------------------------- > > Key: TEIID-3321 > URL: https://issues.jboss.org/browse/TEIID-3321 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.11 > Reporter: Van Halbert > > Support Adabas as a data source -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-57) Criteria ordering

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-57?page=com.atlassian.jira.plugin.s... ] Steven Hawkins resolved TEIID-57. --------------------------------- Resolution: Deferred Barely. It only applies to source systems that have basically no optimization turned on. I'll just set to deferred. > Criteria ordering > ----------------- > > Key: TEIID-57 > URL: https://issues.jboss.org/browse/TEIID-57 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.x > Reporter: Steven Hawkins > > Defect Tracker #24194: The order in which criteria is evaluated in MetaMatrix (and at the source) can have a large impact on performance. We should utilize costing information to order our evaluation of criteria nodes so that the cheapest most limiting criteria is evaluated first. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3608) Add a translator for memcached

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3608?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3608: ----------------------------------- Assignee: Ramesh Reddy > Add a translator for memcached > ------------------------------ > > Key: TEIID-3608 > URL: https://issues.jboss.org/browse/TEIID-3608 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Kylin Soong > Assignee: Ramesh Reddy > Fix For: 9.x > > > memcached can be thought as a standard in Cache area, there are lots of product support memcached, like: > * Infinispan/JBoss Data Grid > * Redis > * Oracle Coherence > * Cassandra > * ... > If we have a memcached translator, it will more flexible in intergrate/transfer data from cache product. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3608) Add a translator for memcached

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3608?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3608: ----------------------------------- Assignee: (was: Ramesh Reddy) > Add a translator for memcached > ------------------------------ > > Key: TEIID-3608 > URL: https://issues.jboss.org/browse/TEIID-3608 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Kylin Soong > Fix For: 9.x > > > memcached can be thought as a standard in Cache area, there are lots of product support memcached, like: > * Infinispan/JBoss Data Grid > * Redis > * Oracle Coherence > * Cassandra > * ... > If we have a memcached translator, it will more flexible in intergrate/transfer data from cache product. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2016