Details
-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
Description
While working with Teiid spring boot starter in my spring boot app I encountered an issue when trying to access spring actuator endpoints.
I have "server.context-path: /api/odata" in my bootstrap.yml configuration.
Then, accessing <my-server-url>/api/odata/health returns an error since I don't have a table named "health":
<error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> <code>null</code> <message> Cannot find EntitySet, Singleton, ActionImport or FunctionImport with name 'health'. </message> </error>
I need to "split" the context for OData endpoints and for the rest endpoints which are not OData endpoints.
I saw that Olingo has a support for that ("org.apache.olingo.odata2.path.split" property).
(didn't find any documentation for that "split" for OData version 4)
https://olingo.apache.org/doc/odata2/tutorials/Olingo_Tutorial_Advanced_Service_Resolution.html
Maybe this feature is useful also for requests which are not OData Protocol requests(and not only for Spring actuator endpoints..)