Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search might require sting parsing #12

Open
chibenwa opened this issue Jun 2, 2017 · 0 comments
Open

Search might require sting parsing #12

chibenwa opened this issue Jun 2, 2017 · 0 comments

Comments

@chibenwa
Copy link
Member

chibenwa commented Jun 2, 2017

Spec says:

The exact semantics for matching String fields is deliberately not defined to allow for flexibility in indexing implementation, subject to the following:

    Text SHOULD be matched in a case-insensitive manner.
    Text contained in either (but matched) single or double quotes SHOULD be treated as a phrase search, that is a match is required for that exact word or sequence of words, excluding the surrounding quotation marks. Use \", \' and \\ to match a literal ", ' and \ respectively in a phrase.
    Outside of a phrase, white-space SHOULD be treated as dividing separate tokens that may be searched for separately in the message, but MUST all be present for the message to match the filter.
    Tokens MAY be matched on a whole-word basis using stemming (so for example a text search for bus would match “buses” but not “business”).

We should avoid having to parse the String, and make this EXPLICIT in the JSON structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant