You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Chandan V.A (JIRA)" <ji...@apache.org> on 2014/11/26 09:41:12 UTC

[jira] [Commented] (OLINGO-491) Query formed has all attributes of JPA entity instead of the selected attributes provided by $select system query option

    [ https://issues.apache.org/jira/browse/OLINGO-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225912#comment-14225912 ] 

Chandan V.A commented on OLINGO-491:
------------------------------------

Hello [~dhaval.gupta],
What do you mean by the query executed by JPA is having all the attributes in the query. You mean the JPQL statements generated by Olingo JPA processor is having all fields included in the JPQL statement or the JPA providers that you are using is generating such a query.

Thanks
Kind 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
>
> 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)