[
https://issues.apache.org/jira/browse/LUCENE-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636409#comment-15636409
]
Michael McCandless commented on LUCENE-7533:
--------------------------------------------
+1 to move towards having proper graphs come out of analysis, and letting query
parsers produce TAQ. I agree there is a lot of work there though :)
Thank you for pointing to LUCENE-6824! I think that issue can be committed ...
it had fallen past the event horizon of my TODO list. I'll revive it ...
> Classic query parser: autoGeneratePhraseQueries=true doesn't work when
> splitOnWhitespace=false
> ----------------------------------------------------------------------------------------------
>
> Key: LUCENE-7533
> URL: https://issues.apache.org/jira/browse/LUCENE-7533
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 6.2, 6.3, 6.2.1
> Reporter: Steve Rowe
> Attachments: LUCENE-7533.patch
>
>
> LUCENE-2605 introduced the classic query parser option to not split on
> whitespace prior to performing analysis.
> From the javadocs for QueryParser.setAutoGeneratePhraseQueries():
> bq.phrase queries will be automatically generated when the analyzer returns
> more than one term from whitespace delimited text.
> When splitOnWhitespace=false, the output from analysis can now come from
> multiple whitespace-separated tokens, which breaks code assumptions when
> autoGeneratePhraseQueries=true: for this combination of options, it's not
> appropriate to auto-quote multiple non-overlapping tokens produced by
> analysis. E.g. simple whitespace tokenization over the query "some words"
> will produce the token sequence ("some", "words"), and even when
> autoGeneratePhraseQueries=true, we should not be creating a phrase query here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
