[ https://issues.apache.org/jira/browse/SOLR-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938935#comment-15938935 ]
Steve Rowe edited comment on SOLR-10310 at 3/23/17 6:13 PM: ------------------------------------------------------------ {{QueryBuilder.autoGenerateMultiTermSynonymsPhraseQuery}}, introduced in LUCENE-7638, is the graph version of {{autoGeneratePhraseQueries}}. I guess there are three possible paths here: # As hinted in SOLR-10348: avoid dealing with sow=false/auto-gen-phrase=true incompatibility by leaving the exception in place and dropping {{autoGeneratePhraseQueries="true"}} from example schemas. # Re-interpret Solr's {{autoGeneratePhraseQueries}} per-fieldtype option as setting {{QueryBuilder.autoGenerateMultiTermSynonymsPhraseQuery}} when {{sow=false}}. # Introduce a new (per-fieldtype?) option {{autoGenerateMultiTermSynonymsPhraseQuery}}. I agree, [~dsmiley], that my #1 above is a step back. (Though [~rcmuir] has claimed otherwise: [https://issues.apache.org/jira/browse/LUCENE-2458?focusedCommentId=12866557&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12866557]) I like #2 best. (Should be done on its own issue though.) Thoughts? was (Author: steve_rowe): {{QueryBuilder.autoGenerateMultiTermSynonymsPhraseQuery()}}, introduced in LUCENE-7638, is the graph version of {{autoGeneratePhraseQueries}}. I guess there are three possible paths here: # As hinted in SOLR-10348: avoid dealing with sow=false/auto-gen-phrase=true incompatibility by leaving the exception in place and dropping {{autoGeneratePhraseQueries="true"}} from example schemas. # Re-interpret Solr's {{autoGeneratePhraseQueries}} per-fieldtype option as setting {{QueryBuilder.autoGenerateMultiTermSynonymsPhraseQuery}} when {{sow=false}}. # Introduce a new (per-fieldtype?) option {{autoGenerateMultiTermSynonymsPhraseQuery}}. I agree, [~dsmiley], that my #1 above is a step back. (Though [~rcmuir] has claimed otherwise: [https://issues.apache.org/jira/browse/LUCENE-2458?focusedCommentId=12866557&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12866557]) I like #2 best. (Should be done on its own issue though.) Thoughts? > By default, stop splitting on whitespace prior to analysis in edismax and > "Lucene"/standard query parsers > --------------------------------------------------------------------------------------------------------- > > Key: SOLR-10310 > URL: https://issues.apache.org/jira/browse/SOLR-10310 > Project: Solr > Issue Type: Task > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Steve Rowe > > SOLR-9185 introduced an option on the edismax and standard query parsers to > not perform pre-analysis whitespace splitting: the {{sow=false}} request > param. > On master/7.0, we should make {{sow=false}} the default. -- 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