You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2016/06/10 19:39:21 UTC

[jira] [Commented] (LUCENE-7315) Flexible "standard" query parser parses on whitespace

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

Michael McCandless commented on LUCENE-7315:
--------------------------------------------

How does this issue differ from LUCENE-2605?

> Flexible "standard" query parser parses on whitespace
> -----------------------------------------------------
>
>                 Key: LUCENE-7315
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7315
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/queryparser
>            Reporter: Steve Rowe
>            Assignee: Steve Rowe
>
> Copied from LUCENE-2605:
> 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