By field aliasing I meant something like: f.all_fields.qf=*_txt+*_s+*_int that would sum up to 100 fields
On Wed, Jun 26, 2013 at 12:00 AM, 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? > >
