[
https://issues.apache.org/jira/browse/LUCENE-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537149#comment-15537149
]
Steve Rowe commented on LUCENE-2605:
------------------------------------
{quote}
I'd like to try out the split-on-whitespace=false without coding, but by
changing a configuration in solrconfig.xml.
Is that possible?
{quote}
Not yet - Solr's "Lucene" aka standard query parser is a fork of the classic
Lucene query parser that was modified on this issue to enable not splitting on
whitespace - Solr doesn't have this support yet. There is a separate issue to
apply the same changes to Solr here: SOLR-9185. I'm working on it.
> queryparser parses on whitespace
> --------------------------------
>
> Key: LUCENE-2605
> URL: https://issues.apache.org/jira/browse/LUCENE-2605
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/queryparser
> Reporter: Robert Muir
> Assignee: Steve Rowe
> Fix For: 6.2
>
> Attachments: LUCENE-2605-dont-split-by-default.patch,
> LUCENE-2605.patch, LUCENE-2605.patch, LUCENE-2605.patch, LUCENE-2605.patch,
> LUCENE-2605.patch, LUCENE-2605.patch
>
>
> 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]
