Hi, Look up edismax parser on the Wiki. The advantage of using it is that you can set different weight on different fields (qf param) and shingle query (pfXXX params).
Otis -- Solr & ElasticSearch Support -- http://sematext.com/ Performance Monitoring -- http://sematext.com/spm On Tue, Jun 25, 2013 at 5:00 PM, Manuel Le Normand <manuel.lenorm...@gmail.com> wrote: > My schema contains about a hundred of fields of various types (int, > strings, plain text, emails). > I was concerned what is the common practice for searching free text over > the index. Assuming there are not boosts related to field matching, these > are the options I see: > > 1. Index and query a "all_fields" copyField source=* > 1. advantages - only one query flow against a single index. > 2. disadvantage - the tokenizing is not necessarily adapted to this > kind of field, this requires more storage and memory > 2. Field aliasing ( f.myalias.qf=realfield) > 1. advantages - opposite from the above > 2. disadvantages - a single query term would query 100 different > fields. Multi term query might be a serious performance issue. > > Any common practices?
