The JPA Processor fills the gap between Olingo V4 and the database, by providing a mapping between JPA metadata and OData metadata, generating queries and supporting the entity manipulations.
Apache License 2.0
122
stars
76
forks
source link
Add protection where clause to ElementCollections of Embeddable entities as well #157
As an initial mitigation to the performance problems described here: https://github.com/SAP/olingo-jpa-processor-v4/issues/154 we can add protection where clause to sub-entities as well in order to limit the response for a dedicated tenancy as well. Otherwise the whole tables are loaded in memory for entities that we are sure won't match any of the parent entities due to protection restrictions.
As an initial mitigation to the performance problems described here: https://github.com/SAP/olingo-jpa-processor-v4/issues/154 we can add protection where clause to sub-entities as well in order to limit the response for a dedicated tenancy as well. Otherwise the whole tables are loaded in memory for entities that we are sure won't match any of the parent entities due to protection restrictions.