You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Chandan V.A (JIRA)" <ji...@apache.org> on 2015/11/27 04:26:10 UTC

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

     [ https://issues.apache.org/jira/browse/OLINGO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chandan V.A reassigned OLINGO-829:
----------------------------------

    Assignee: Chandan V.A

> 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.3.4#6332)