[
https://issues.apache.org/jira/browse/SOLR-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946111#comment-15946111
]
ASF subversion and git services commented on SOLR-10357:
--------------------------------------------------------
Commit da2cfda02fe539c42f1794fc56a478a3acc7d111 in lucene-solr's branch
refs/heads/branch_6x from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=da2cfda ]
SOLR-10357: Enable edismax and standard query parsers to handle the option
combination sow=false / autoGeneratePhraseQueries=true by setting
QueryBuilder.autoGenerateMultiTermSynonymsQuery
> When sow=false, edismax&standard query parsers should handle per-fieldtype
> autoGeneratePhraseQueries by setting
> QueryBuilder.autoGenerateMultiTermSynonymsQuery
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-10357
> URL: https://issues.apache.org/jira/browse/SOLR-10357
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Steve Rowe
> Attachments: SOLR-10357.patch, SOLR-10357.patch, SOLR-10357.patch
>
>
> Right now, the options to not split on whitespace ({{sow=false}}) and to
> autogenerate phrase queries ({{autoGeneratePhraseQueries="true"}}) will cause
> queries to throw an exception, since they are incompatible.
> {{QueryBuilder.autoGenerateMultiTermSynonymsPhraseQuery}}, introduced in
> LUCENE-7638, is the graph query version of Solr's per-fieldtype
> {{autoGeneratePhraseQueries}} option, and is not incompatible with
> {{sow=false}}.
> So {{autoGeneratePhraseQueries="true"}} should cause
> {{QueryBuilder.autoGenerateMultiTermSynonymsPhraseQuery}} to be set to true
> when {{sow=false}}, rather than triggering an exception.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
