[
https://issues.apache.org/jira/browse/OLINGO-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263520#comment-14263520
]
Chandan V.A commented on OLINGO-491:
------------------------------------
Hi Dhaval,
It is by design JPQL queries are constructed without SELECT expression, to
avoid complexity involved in constructing the JPQL queries because we also need
to consider properties that are accessed via Naviagtion property while
constructing the JPQL select expression, provided those properties appear in
$select expression. To keep the logic simple currently no select expression is
built for JPQL statements.
Regards
Chandan
> Query formed has all attributes of JPA entity instead of the selected
> attributes provided by $select system query option
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: OLINGO-491
> URL: https://issues.apache.org/jira/browse/OLINGO-491
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Reporter: dhaval gupta
> Assignee: Chandan V.A
> Fix For: V2 2.0.2
>
>
> Query formed has all attributes of JPA entity instead of the selected
> attributes provided by $select system query option.
> For ex :
> Suppose we have entity Issue in which there are 20 attributes. Now I select 2
> attributes out of those 20 by $select=assetCode, IdIsin but the query that is
> executed by JPA is having all the 20 attributes in the query .
> Thanks
> Dhaval
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
