A user reported that they were frustrated that their search results totally changed when they changed the casing of their query. See the below screenshots. It would be nice if we could do better than this since, for example, Google is totally case insensitive for this same query.
Description
Description
Event Timeline
Comment Actions
The examples show a WrestleReunion and an E57.
CirrusSearch tokenizer creates term boundaries terms inside camelCase and 4tokenizing forms.
It matters whether there were "quotes" around the search term.
Please ask at the talk page of CirrusSearch, where someone should be obligagated to say:
| - | parserfunction | parserFunction | parser function | parser-function | Note |
|---|---|---|---|---|---|
| parserfunction | Yes | Yes | No | No | Case insensitive |
| "parser function" | No | No | Yes | Yes | Case insensitive |
| parser_function | No | Yes | Yes | Yes | Case insensitive |
| parserFunction | Yes | Yes | Yes | Yes | Case insensitive |
Comment Actions
Interestingly, the completion suggester does much better at this; the only result for both queries listed in the example is "It Follows", which is pretty correct.