[ 
https://issues.apache.org/jira/browse/SOLR-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Rowe updated SOLR-10357:
------------------------------
    Attachment: SOLR-10357.patch

Patch implementing the idea.  

There remains an issue: the original auto-gen use case (for e.g. {{wifi => wi 
fi}}, replacing a single token with multiple tokens, but no overlapping terms) 
still doesn't auto-generate a phrase query for `wi fi` if synonyms are replaced 
rather than expanded when  {{QueryBuilder.autoGenerateMultiTermSynonymsQuery}} 
is set to {{true}}.  So this is not (yet) a complete solution.  IMHO this is a 
weakness of how {{QueryBuilder}} decides whether to invoke "graph" processing, 
currently only when a posLength > 1 is encountered (as when there are 
*overlapping* multi-word synonyms).

This patch changes the test schema named {{schema12.xml}} to use the 
graph-aware versions of the synonym and word delimiter filters.  Instead of 
committing as-is (pending full testing and precommit, not yet done), I'll do 
the rote schema conversions on SOLR-10343 and SOLR-10344 and set those as 
blockers of this issue; that seems like a more appropriate way to handle 
whatever conflicts might come up from other uses of {{schema12.xml}}.

> 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
>
>
> 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]

Reply via email to