Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Fri, 30 Sep 2016 20:46:20 +0000 (UTC)
From: "Dion Olsthoorn (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12471774.1282015826000.711884.1475268380722@Atlassian.JIRA>
In-Reply-To: <JIRA.12471774.1282015826000@Atlassian.JIRA>
References: <JIRA.12471774.1282015826000@Atlassian.JIRA> <JIRA.12471774.1282015826118@arcas>
Subject: [jira] [Commented] (LUCENE-2605) queryparser parses on whitespace
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 30 Sep 2016 20:46:23 -0000


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

Dion Olsthoorn commented on LUCENE-2605:
----------------------------------------

Thanks for quick response, Steve. I overlooked your last patch was for master only, not for 6.x.
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: 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