You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Ramya (Jira)" <ji...@apache.org> on 2020/01/14 09:28:00 UTC

[jira] [Commented] (OLINGO-1417) OData V4: Adopt search option based on new V4 abnf

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

Ramya commented on OLINGO-1417:
-------------------------------

Few more changes as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=1df2f4aa67e9ed5c3cc10f3abc65f9e1fd7ee042

>  OData V4: Adopt search option based on new V4 abnf
> ---------------------------------------------------
>
>                 Key: OLINGO-1417
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1417
>             Project: Olingo
>          Issue Type: Improvement
>          Components: odata4-server
>            Reporter: Ramya
>            Priority: Major
>             Fix For: (Java) V4 4.7.1
>
>
> The ABNF for V4 was overly restrictive for search system query option, this got fixed lated in https://github.com/oasis-tcs/odata-abnf/blob/master/abnf/odata-abnf-construction-rules.txt#L332-L356.
> Numbers are fine, as are numbers with decimal point or decimal comma, minus signs, and any percent-encoded Unicode character from categories Letter (L) and Number (N).
> The library should be enhanced to support this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)