Skip to content

Search might require sting parsing #12

@chibenwa

Description

@chibenwa

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions