]
Ramesh Reddy commented on TEIID-3911:
-------------------------------------
This is worked under upstream as
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).