[
https://issues.apache.org/jira/browse/SOLR-9185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325683#comment-15325683
]
Yonik Seeley commented on SOLR-9185:
------------------------------------
bq. The current behavior might be counter to a new user's expectations, but if
we just change how it works by default, a lot of existing users might suddenly
be surprised by very different behavior from Solr
+1, it's been this way since the beginning of Lucene. It's not a bug (esp
since in the past multiple terms were treated as a phrase query, and still are
depending on configuration - think word delimiter filter).
bq. I suppose we could add luceneMatchVersion-sensitive code
That's a very blunt hammer ;-)
It would be nice if we could selectively keep the old behavior, but I'm not
sure how difficult that would be w/o duplicating the whole parser.
> Solr's "Lucene"/standard query parser should not split on whitespace before
> sending terms to analysis
> -----------------------------------------------------------------------------------------------------
>
> Key: SOLR-9185
> URL: https://issues.apache.org/jira/browse/SOLR-9185
> Project: Solr
> Issue Type: Bug
> Reporter: Steve Rowe
> Assignee: Steve Rowe
>
> 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'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
