[
https://issues.apache.org/jira/browse/OLINGO-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263587#comment-14263587
]
dhaval gupta commented on OLINGO-491:
-------------------------------------
Thanks Chandan for the comments.
Suppose there is one table having 300 attributes and if the user selects just
10 attributes , there is database cost paid in executing query with 290 extra
attributes(not requested by user) which in turn affects the overall performance.
Not implementing select expression may help us in keeping logic simple but it
is at the cost of performance which should not be the case in my opinion.
Let me know if you have some other opinion.
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
> 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)
