[
https://issues.apache.org/jira/browse/OLINGO-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093848#comment-14093848
]
Michael Bolz commented on OLINGO-388:
-------------------------------------
Hi [~cholzer],
I also started to investigate this issue and you are right about OData V2,
OData V4 and Microsofts implementation.
So I think we should handle duplicate {{system query options}} in OData V2 /
Olingo V2 in the same way as in OData V4 and respond with a {{400 - Bad
Request}}.
I will check your contribution and if all fits I create an according commit.
Kind regards,
Michael
> Duplicate System Query Options do not result in an exception
> ------------------------------------------------------------
>
> Key: OLINGO-388
> URL: https://issues.apache.org/jira/browse/OLINGO-388
> Project: Olingo
> Issue Type: Wish
> Affects Versions: V2 2.0.0
> Reporter: Christian Amend
> Assignee: Michael Bolz
> Priority: Minor
> Fix For: V2 2.0.1
>
> Attachments: olingo-388.diff
>
>
> If a System Query Option is given twice e.g. $top=3 and $top=4 we take the
> last query option and do not throw an exception. The specification is not
> clear on this but we could be more strict here.
> Clarifiy on dev list if this should be fixed and how. (Maybe through
> configuration to not break existing scenarios)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
