From solr-user-return-36061-apmail-lucene-solr-user-archive=lucene.apache.org@lucene.apache.org Wed May 12 19:09:02 2010 Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 88449 invoked from network); 12 May 2010 19:09:01 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 May 2010 19:09:01 -0000 Received: (qmail 76111 invoked by uid 500); 12 May 2010 19:08:59 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 76083 invoked by uid 500); 12 May 2010 19:08:59 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 76075 invoked by uid 99); 12 May 2010 19:08:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 19:08:59 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.236.158 is neither permitted nor denied by domain of ahmed.hammad@gmail.com) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 19:08:52 +0000 Received: from ben.nabble.com ([192.168.236.152]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1OCHIG-00043G-3Y for solr-user@lucene.apache.org; Wed, 12 May 2010 12:08:32 -0700 Date: Wed, 12 May 2010 12:08:32 -0700 (PDT) From: ahammad To: solr-user@lucene.apache.org Message-ID: <1273691312102-813275.post@n3.nabble.com> In-Reply-To: References: Subject: Re: multi-valued associated fields MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I had the same problem as you last year, i.e. indexing stuff from different sources with different characteristics. The way I approached it is by setting up a multi-core environment, with each core representing one type of data. Within each core, I had a "data type" sort of field that would define what kind of data is stored (i.e. in your case, it would be "auto" or "real estate" etc...). The advantages of this setup is that it allows you to make changes to individual cores without affecting anything else. Also, faceting based on category is achieved by the data type field. You can do searching on multiple cores like you would on a single core, meaning that all the search parameters can be applied. Solr will automatically merge all the data into one result set. Another advantage is if you index frequently, this way will allow you to index at different times and reduce the overall load. Just a thought an an approach... -- View this message in context: http://lucene.472066.n3.nabble.com/multi-valued-associated-fields-tp811883p813275.html Sent from the Solr - User mailing list archive at Nabble.com.