[
https://issues.apache.org/jira/browse/OLINGO-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Amend updated OLINGO-568:
-----------------------------------
Description:
The OData V4 specification describes a System Query Option called $search as
follows: "The $search system query option allows clients to request entities
matching a free-text search expression."
In scope of this JIRA item we would like to implement a parser which can parse
such query strings and provide them to an application in an understandable
manner.
This issue could be implemented by a Student who takes part in the GSoC as it
is a very isolated topic within the Olingo V4 server library. It would still
require a broad knowledge of the OData topic to be an opportunity to learn. The
scope for the GSoC does not need to include all subtasks which are currently
attached to this issue. If you are interested comment this issue or write a
mail to [email protected]
Sources:
V4 Specification:
http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part2-url-conventions/odata-v4.0-errata02-os-part2-url-conventions-complete.html#_Toc405999475
Olingo Website: http://olingo.apache.org/
OData.org: http://www.odata.org/
was:
The OData V4 specification describes a System Query Option called $search as
follows: "The $search system query option allows clients to request entities
matching a free-text search expression."
In scope of this JIRA item we would like to implement a parser which can parse
such query strings and provide them to an application in an understandable
manner.
This issue could be implemented by a Student who takes part in the GSoC as it
is a very isolated topic within the Olingo V4 server library. It would still
require a broad knowledge of the OData topic to be an oppertunity to learn. The
scope for the GSoC does not need to include all subtasks which are currently
attached to this issue. If you are interested comment this issue or write a
mail to [email protected]
Sources:
V4 Specification:
http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part2-url-conventions/odata-v4.0-errata02-os-part2-url-conventions-complete.html#_Toc405999475
Olingo Website: http://olingo.apache.org/
OData.org: http://www.odata.org/
> OData $search Query Parser for Olingo
> -------------------------------------
>
> Key: OLINGO-568
> URL: https://issues.apache.org/jira/browse/OLINGO-568
> Project: Olingo
> Issue Type: New Feature
> Components: odata4-server
> Affects Versions: (Java) V4 4.0.0-beta-02
> Reporter: Christian Amend
> Labels: gsoc2015, java, mentor, odata
>
> The OData V4 specification describes a System Query Option called $search as
> follows: "The $search system query option allows clients to request entities
> matching a free-text search expression."
> In scope of this JIRA item we would like to implement a parser which can
> parse such query strings and provide them to an application in an
> understandable manner.
> This issue could be implemented by a Student who takes part in the GSoC as it
> is a very isolated topic within the Olingo V4 server library. It would still
> require a broad knowledge of the OData topic to be an opportunity to learn.
> The scope for the GSoC does not need to include all subtasks which are
> currently attached to this issue. If you are interested comment this issue or
> write a mail to [email protected]
> Sources:
> V4 Specification:
> http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part2-url-conventions/odata-v4.0-errata02-os-part2-url-conventions-complete.html#_Toc405999475
> Olingo Website: http://olingo.apache.org/
> OData.org: http://www.odata.org/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
