Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of idokissos@gmail.com
 designates 74.125.82.43 as permitted sender)
MIME-Version: 1.0
Sender: idokissos@gmail.com
From: Manuel Le Normand <manuel.lenormand@gmail.com>
Date: Wed, 26 Jun 2013 00:00:30 +0300
Message-ID: 
 <CABGq8w90SJUpQAEpF0jtqh+gkEmvBdOCMLRJZwS0feXiVzsLsg@mail.gmail.com>
Subject: Common practice for free text field
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=f46d0438934b8a040b04e000d39a

--f46d0438934b8a040b04e000d39a
Content-Type: text/plain; charset=ISO-8859-1

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?

--f46d0438934b8a040b04e000d39a--