On 7/20/2018 8:33 AM, Krishnan, Deepti (NIH/OD) [C] wrote: > > We are working on a .net application using Solr. When we initially > launched the site we were using the 5.5.3 version and last sprint we > updated it to the 7.3.1 version. Everything is working fine ass > expected expect for one feature. > > > > The exact phrase search does not return any value for some search > criteria, and this used to work fine with the older version. Based on > our research, those search terms with stop words and more than one > word following it is not working. > > > > The field has been defined as a text_general type in the schema and > below are the tokenizers and filters used during indexing and querying. >
Your image did not make it to the list. Can't see it. To test a theory, try adding a sow parameter set to true to the request. I have no idea how to do this in a .net application, but if it were a URL in a browser, you would add "&sow=true" (without the quotes) to the URL. If that works, I am not sure whether it's a bug or not, but you'll have a workaround. The sow parameter was added in one of the 6.x releases with the default value set to true. In 7.0, the default value was changed to false. The parameter is shorthand for "split on whitespace". When sow=false, phrase queries do not appear to work correctly. https://lucene.apache.org/solr/guide/7_4/the-standard-query-parser.html#standard-query-parser-parameters Thanks, Shawn
