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

Jim Ferenczi commented on LUCENE-7799:
--------------------------------------

Then we should maybe remove {{autoGenerateMultiTermSynonymsPhraseQuery}} and 
make {{autoGeneratePhraseQueries}} applicable to graph and non-graph query even 
when {{splitOnWhitespace=false}}. A nice side effect of this change is that it 
would correctly handle a simple synonym rule like "ny, new york". With 
{{autoGeneratePhraseQueries=true}} "new york" would be matched as a phrase 
query with the input query "ny" and as a simple disjunction with the input 
query "new york". Of course this should also be true when "ny" is preserved in 
the output (when graph processing is involved) which is why I think it is 
important to have a single option for graph and non-graph query.


> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to