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] (ODATA-1100) Add mechanism for specifying match type for $search

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

Mark Biamonte updated ODATA-1100:

    Resolution: This issue was closed with no action.  The feed back from users was that defining our own syntax in the $search query parameter was not desired.  Users would rather use the syntax defined by existing popular search engines vs OData defining yet another one.  Issue OData-1113 Allow alternate / native search syntax was created for the 4.02 specification to investigate this further.

> Add mechanism for specifying match type for $search
> ---------------------------------------------------
>                 Key: ODATA-1100
>                 URL: https://issues.oasis-open.org/browse/ODATA-1100
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: Protocol
>    Affects Versions: V4.01_CSD02
>            Reporter: Mark Biamonte
>            Assignee: Mark Biamonte
>             Fix For: V4.01_CS01
> When doing text searches, many of the common algorithms we use have a number of different ways to define a match (Exact match, begins with, synonym, base word or inflection, etc).  The spec currently says it is up to the implementation as to what constitutes a match, this is fine, but in the case where the search algorithm provides different matching types it would be nice if the query writer could specify the type of match they want in the $search expression.

This message was sent by Atlassian JIRA

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