[SOLR-9185] Solr's edismax and "Lucene"/standard query parsers should optionally not split on whitespace before sending terms to analysis

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.5, 7.0
• Assignee: Steven Rowe
• Reporter: Steven Rowe
• Created: 04/Jun/16 00:40
• Updated: 27/Mar/18 18:31
• Resolved: 17/Mar/17 00:37

Description

Copied from LUCENE-2605:

The queryparser parses input on whitespace, and sends each whitespace separated term to its own independent token stream.

This breaks the following at query-time, because they can't see across whitespace boundaries:

n-gram analysis
shingles
synonyms (especially multi-word for whitespace-separated languages)
languages where a 'word' can contain whitespace (e.g. vietnamese)

Its also rather unexpected, as users think their charfilters/tokenizers/tokenfilters will do the same thing at index and querytime, but
in many cases they can't. Instead, preferably the queryparser would parse around only real 'operators'.

Issue Links

• is duplicated by: SOLR-5379 Query-time multi-word synonym expansion
• is related to: SOLR-5379 Query-time multi-word synonym expansion
• is related to: SOLR-4381 Query-time multi-word synonym expansion
• is related to: SOLR-10310 By default, stop splitting on whitespace prior to analysis in edismax and "Lucene"/standard query parsers
• is related to: SOLR-10348 unexpected sow=false interaction with defaultSearchField
• relates to: LUCENE-2605 queryparser parses on whitespace