alessandrobenedetti edited a comment on pull request #129: URL: https://github.com/apache/solr/pull/129#issuecomment-857896432
> iiuc there'd be no way to migrate current behavior for anyone who wanted to preserve it Mmmm if you want to split on whitespace for a field in QF that is a StrField, you can just use sow=true. I am not suggesting we should remove sow=true for StrFields, the objective here is to fix sow=false. The reason I am saying that currently in my opinion we have a problem is that if you do: Given q=<term1 term2> **sow=true** -> StrField:term1 StrField:term2 **sow=false** -> StrField:term1 StrField:term2 As a user (my personal idea) if I set a StrFIeld in QF and set sow=false, I am relying on the query time tokenization approach of my QF fields (and query time tokenization approach for a StrField is "not to tokenize at all") So if I have multi terms in the index for my StrField e.g. StrField: "term1 term2", currently I am unable to search for them both using sow=true or sow=false. On the other hand if I have in my index [Doc1 StrField:"term1"] [Doc2 StrField:"term2"], for the query "term1 term2" I'll make sure to configure my sow=true. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
