You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Michael Bolz (JIRA)" <ji...@apache.org> on 2014/11/25 06:31:12 UTC

[jira] [Commented] (OLINGO-496) Throw UriSyntaxException with INCOMPATIBLESYSTEMQUERYOPTION when $orderby param is specified for $count URI

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

Michael Bolz commented on OLINGO-496:
-------------------------------------

Hi [~kiransg],

for a first look your suggestion make sense.
 [~koblers]: As expert for {{UriParserImpl}} can you tell us your opinion?

Kind regards,
Michael

> Throw UriSyntaxException with INCOMPATIBLESYSTEMQUERYOPTION when $orderby param is specified for $count URI
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: OLINGO-496
>                 URL: https://issues.apache.org/jira/browse/OLINGO-496
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-core, odata2-jpa
>    Affects Versions: V2 2.0.0
>            Reporter: Kiran G
>            Assignee: Michael Bolz
>            Priority: Minor
>
> UriParserImpl should block the urls for form _/Entities/$count?$orderby=<attr>_, as it doesn't make sense to pass orderby for a count query.
> This breaks the odata-jpa implementation as the count query gets generated along with the order by clause.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)