This is a short blog about the limitations of Olingo oData 2.0, Which i came across while implementing the Olingo OData 2. Refer the previous blogs on Olingo OData 2.0 implementations using JPA based applications.
- As of now, aggregations is not possible with Apache Olingo OData 2.0.
- Calculation views in Apache Olingo OData 2.0 exposed as tables unlike XSODATA.
- Getting metadata of calculation views is still not possible with Olingo OData 2.0 as it assumes the calculation view as tables in Java.
Still we can modify the metadata of calculation views by custom annotations approach in JAVA. Which I have already implemented by using custom annotations In that case whenever any changes in the calculation view has to be added in the JAVA. The limitations would be that we may have the metadata like XSODATA but aggregations and dimensions is not possible with the current versions.
As of now I have came across through these limitations only but, I will keeping updating this blog based on any new limitations which I came across.
If anyone came across any new issue, Please post in the comment sections.
Few of my other blog posts:-
- Blog Series:ODATA Protocol implementation for IOT Applications on SAP HCP
- Binary content upload & download from HANA DB via Apache Olingo OData in SCP
- Database migration in SAP Cloud platform using Liquibase
- Image persistence through Spring RESTful web services in CF
- logging in SCP with Java and Tomee using slf4j, logback, Jolokia
- Json to parquet, orc file format using Apache spark library
- Introduction to Annotations & Vocabularies
- Annotation’s usage in SAP S/4HANA Intelligent product design