[ https://issues.apache.org/jira/browse/SOLR-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939335#comment-15939335 ]
Steve Rowe commented on SOLR-10310: ----------------------------------- bq. #2 and #3 are pretty similar and not even mutually exclusive . In #3 you're just saying give this option a more appropriate name I guess. #3 is essentially a back-compat break that would force users to change field type config away from {{autoGeneratePhraseQueries="true"}} to {{autoGenerateMultiTermSynonymsPhraseQuery="true"}} in order to invoke this option for graph-based queries (assuming {{sow=false}} and graph-aware token filters). bq. #3 makes sense but I wonder if the FieldType is the right place for these query building options; shouldn't it be request params? {{autoGeneratePhraseQueries}} is already a FieldType option. Putting it (or its graph-based replacement, i.e. #3) somewhere else would be another step back. > 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