You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Ramesh Reddy (JIRA)" <ji...@apache.org> on 2014/09/19 17:53:33 UTC

[jira] [Commented] (OLINGO-434) Unary parsing is not complete in UriParseTreeVisitor

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

Ramesh Reddy commented on OLINGO-434:
-------------------------------------

>From GitHub patch and diff files
https://github.com/rareddy/olingo-odata4/commit/b45e3473a7ade5323776b79ed60458a3332946a5.patch
https://github.com/rareddy/olingo-odata4/commit/b45e3473a7ade5323776b79ed60458a3332946a5.diff

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