OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Updated: (ODATA-228) Specify $search for free-text search within a OData Service and specify $search for free-text search within an entityContainer


     [ http://tools.oasis-open.org/issues/browse/ODATA-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-228:
-----------------------------

       Proposal: 
Support $search on
 (1) Service level (scope of search is the complete service) 
 (2) EntityContainer level (scope of search is a specific entityContainer)

Search query syntax is exactly like in ODATA-139.
  (1) Example URL  ~/somePath/odata/netbay.svc?$search=$search=foo AND bar
  (2) Example URL  ~/somePath/odata/netbay.svc/containerName?$search=$search=foo OR bar

The result is a feed containing entities from that service or container. As there's no common type on feed level, the entities contain an odata.type annotation in JSON responses, and an <atom:category> element in Atom responses.
    Environment: [Proposed]
    Description: 
Exactly the same as in https://tools.oasis-open.org/issues/browse/ODATA-139; the only difference is, that ODATA-139 limits the scope of the $search to a specific entity set. 


  was:
Exactly the same as in https://tools.oasis-open.org/issues/browse/ODATA-139; the only difference is, that ODATA-139 limits the scope of the $search to a specific entitySet. 
The Proposal is to 
 (1) support $search on Service level (scope of search is the complete service) 
 (2) support $search on entityContainer level (scope of search is a specific entityContainer)

Search query syntax is exactly like in ODATA-139.
  (1) Example URL  ~/somePath/odata/netbay.svc?$search=$search=foo AND bar
  (2) Example URL  ~/somePath/odata/netbay.svc/containerName?$search=$search=foo OR bar

To be defined: How should the result payload be structured?


> Specify $search for free-text search within a OData Service and specify $search for free-text search within an entityContainer
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-228
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-228
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules v1.0, OData Protocol v1.0, OData URL Conventions v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Martin Zurmuehl
>            Priority: Minor
>
> Exactly the same as in https://tools.oasis-open.org/issues/browse/ODATA-139; the only difference is, that ODATA-139 limits the scope of the $search to a specific entity set. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]