We are using solr 5.4.0 in the production environment. we are planning to migrate to solr 8.5.
We have observed that in solr 8.5 if we keep `sow`(split on whitespace) parameter as false(default) query is parsed as field-centric and if `sow` is marked as true query is parsed as term-centric. Our search application is more suited to term-centric match (with minimum should match set as 100%) and we want to continue using that. Currently, we are using edismax query parser and documents are ranked/matched/boosted using qf (Query Fields) for term match and pf (Phrase Fields) for phrase matching. Along with term/phrase matching, we want to add exact matching functionality. For this, we decided to define a field (say 'exact_match') using KeywordTokenizerFactory. But the problem over here is `sow` parameter. If we keep `sow` as true (which is required for term-centric match in solr 8.5) query terms are tokenized on whitespace before sending for matching on exact_match field. Is there any way we can keep using term-centric match and also support exact matching? We have found one workaround for this: We append <start> and <end> token to the field value while indexing and during query time we append same <start> and <end> token to the query terms(s) and use phrase matching. Since phrase matching is expensive as compared to keyword (exact) match. We are looking for a way to support exact_match and also have term-centric matching. I also found one jira ticket which is loosely related to this. https://issues.apache.org/jira/browse/SOLR-12779 -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
