[
https://issues.apache.org/jira/browse/OLINGO-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz resolved OLINGO-434.
---------------------------------
Resolution: Fixed
Fix Version/s: (Java) V4 4.0.0-beta-02
[Fixed and
merged|https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=541d76652e25c1f8ccbfa23cd07b98f180532261].
For more comments see OLINGO-435
Kind regards,
Michael
> Unary parsing is not complete in UriParseTreeVisitor
> ----------------------------------------------------
>
> Key: OLINGO-434
> URL: https://issues.apache.org/jira/browse/OLINGO-434
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Reporter: Ramesh Reddy
> Assignee: Michael Bolz
> Priority: Critical
> Fix For: (Java) V4 4.0.0-beta-02
>
> Attachments: olingo-odata4.patch
>
>
> Currently if you have a Unary clause like
> {code}
> /service/EntitySet?$filter=not(x)
> {code}
> This is not properly handled in UriParseTreeVisitor and as result the Unary
> operator is dropped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
