[
https://issues.apache.org/jira/browse/OLINGO-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226459#comment-14226459
]
dhaval gupta commented on OLINGO-491:
-------------------------------------
Hi Chandan,
I mean the JPQL statements generated by the Olingo JPA processor.
For example :
/Issues?$select=IdIsin,AssetCode,BbTicker&$filter=AssetCode eq 'FI'
For above request the JPQL statement generated by Olingo JPA processor is
having all the attributes of Issue entity but it should contain only the
attributes provided by the $select system query option.
Thanks
Dhaval.
> 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
>
> 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 .
> The same thing is happening with function import as well when we write own
> JPA query.
> Thanks
> Dhaval
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
