lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-2605) queryparser parses on whitespace
Date Fri, 30 Sep 2016 19:16:21 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15536784#comment-15536784
] 

Steve Rowe commented on LUCENE-2605:
------------------------------------

Hi [~dionoid]

bq. Reading the discussion above, it seems that splitting on whitespace is disabled by default
now.

No, that's wrong - from the commit messages (which you can see in comments on this issue above):

bq. Default behavior remains unchanged: split-on-whitespace=true

In Lucene 7.0, though, the default before will switch to split-on-whitespace=false

{quote}
How can I test if this works?
Any example configuration would be very helpful!
{quote}

Have you tried setting [{{setSplitOnWhitespace(false)}}|http://lucene.apache.org/core/6_2_1/queryparser/org/apache/lucene/queryparser/classic/QueryParser.html#setSplitOnWhitespace-boolean-]
on the query parser before using 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message