lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dion Olsthoorn (JIRA)" <>
Subject [jira] [Commented] (LUCENE-2605) queryparser parses on whitespace
Date Fri, 30 Sep 2016 20:46:20 GMT


Dion Olsthoorn commented on LUCENE-2605:

Thanks for quick response, Steve. I overlooked your last patch was for master only, not for
I'd like to try out the split-on-whitespace=false without coding, but by changing a configuration
in solrconfig.xml.

Is that possible?

> queryparser parses on whitespace
> --------------------------------
>                 Key: LUCENE-2605
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message