Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 11 Jun 2012 02:54:44 +0000 (UTC)
From: "John Berryman (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <1975259931.1945.1339383284121.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Comment Edited] (LUCENE-2605) queryparser parses on
 whitespace
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

John Berryman edited comment on LUCENE-2605 at 6/11/12 2:53 AM:
----------------------------------------------------------------

subscribed - Current client has index full of clothing - a search for "dress shoes" will return results containing womens' dresses and running shoes. That's not really acceptable.
                
      was (Author: berryman):
    subscribed - Current client has index full of clothing - a search for "dress shoes" will return results containing womens' dresses and running shoes.
                  
> queryparser parses on whitespace
> --------------------------------
>
>                 Key: LUCENE-2605
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2605
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: core/queryparser
>            Reporter: Robert Muir
>             Fix For: 4.1
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org