Aman, Use a copyfield so you can have a second field that uses a different analysis chain. In the new field you just created for the copyfield, use the lowercase type, or create a type using KeywordTokenizer in the analysis chain. Then match on the original field, and boost based on the new field. Cheers Rick
On June 19, 2017 11:01:49 AM EDT, Aman Deep Singh <amandeep.coo...@gmail.com> wrote: >Yes alessandro, >I know that their us some downsight of using sow =false but if don't >use >it then neither shingle nor bhram will work ,and these are required in >my >case/setup > >On 19-Jun-2017 8:18 PM, "alessandro.benedetti" <a.benede...@sease.io> >wrote: > >Isn't this a case where you don't want the query parser to split by >space >before the analyser ? >Take a look to the "sow" param for the edismax query parser. >In your case you should be ok but Be aware that is not a silver bullet >for >everything and that other problems could arise in similar scenarios >[1]. > >The *sow* Parameter >Split on whitespace: if set to false, whitespace-separated term >sequences >will be provided to text analysis in one shot, enabling proper function >of >analysis filters that operate over term sequences, e.g. multi-word >synonyms >and shingles. Defaults to true: text analysis is invoked separately for >each >individual whitespace-separated term. > >[1] >http://lucene.472066.n3.nabble.com/The-downsides-of- >not-splitting-on-whitespace-in-edismax-the-old-albino- >elephant-prob-td4327440.html > > > >----- >--------------- >Alessandro Benedetti >Search Consultant, R&D Software Engineer, Director >Sease Ltd. - www.sease.io >-- >View this message in context: http://lucene.472066.n3. >nabble.com/Give-boost-only-if-entire-value-is-present-in- >Query-tp4341714p4341735.html >Sent from the Solr - User mailing list archive at Nabble.com. -- Sorry for being brief. Alternate email is rickleir at yahoo dot com
