You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2017/04/21 23:29:04 UTC
[jira] [Updated] (LUCENE-7799) Classic query parser should allow
autoGeneratePhraseQueries=true when splitOnWhitespace=false
[ https://issues.apache.org/jira/browse/LUCENE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Rowe updated LUCENE-7799:
-------------------------------
Component/s: core/queryparser
> Classic query parser should allow autoGeneratePhraseQueries=true when splitOnWhitespace=false
> ---------------------------------------------------------------------------------------------
>
> Key: LUCENE-7799
> URL: https://issues.apache.org/jira/browse/LUCENE-7799
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/queryparser
> Reporter: Steve Rowe
>
> LUCENE-7533 disabled the option combination {{splitOnWhitespace=false}}/{{autoGeneratePhraseQueries=true}} because of how {{autoGeneratePhraseQueries=true}} is handled: a query chunk is treated as if it were literally quoted. When {{splitOnWhitespace=false}}, a query chunk can be multiple whitespace-separated words, and auto-quoting multiple terms will produce inappropriate phrase queries.
> I have an idea about how to fix this: {{autoGeneratePhraseQueries=true}} is supposed to cause phrase queries to be constructed when multiple analyzed terms result from a single query word, e.g. when WordDelimiter(Graph)Filter splits words up. Maybe this could be re-implemented in terms of offsets, since all terms from the same original term share the same offsets.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org