[jira] [Commented] (OLINGO-829) Olingo JPA chokes on filter expression

["Ramya (JIRA)" <ji...@apache.org>]

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

Ramya commented on OLINGO-829:
------------------------------

The fix is available as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=85c993f1ccb3cdbd7d90a26bb1eefee8430b3656

Please verify and get back if issue still exists.

Regards,
Ramya

> Olingo JPA chokes on filter expression
> --------------------------------------
>
>                 Key: OLINGO-829
>                 URL: https://issues.apache.org/jira/browse/OLINGO-829
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-jpa
>    Affects Versions: V2 2.0.6
>         Environment: EclipseLink JPA provider
>            Reporter: Richard Birenheide
>            Assignee: Chandan V.A
>
> Olingo JPA chokes on the following filter expression:
> $filter=startswith(ABAPReference,%27TEST%27)%20and%20(ABAPReferenceType%20eq%20%27DataElement%27)
> with
> <innererror>
> class org.apache.olingo.odata2.jpa.processor.api.exception.ODataJPARuntimeException : "org.apache.olingo.odata2.jpa.processor.core.ODataExpressionParser: "OData - JPA Runtime: OData Expression parser - Operator EQ or NE missing". "
> </innererror>
> whereas the following
> $filter=(ABAPReferenceType%20eq%20%27DataElement%27)%20and%20startswith(ABAPReference,%27TEST%27)
> works fine. Just the order of the 'and' expression parts is reversed. Unfortunately we use a frontend library which generates the expression automatically. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)