Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 28241 invoked from network); 26 Mar 2007 16:03:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Mar 2007 16:03:24 -0000 Received: (qmail 36494 invoked by uid 500); 26 Mar 2007 16:03:25 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 36359 invoked by uid 500); 26 Mar 2007 16:03:24 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 36348 invoked by uid 99); 26 Mar 2007 16:03:24 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2007 09:03:24 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [128.230.18.29] (HELO mailer.syr.edu) (128.230.18.29) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2007 09:03:15 -0700 Received: from [128.230.84.100] (ist-h335-d03.syr.edu) by mailer.syr.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.160F7497@mailer.syr.edu>; Mon, 26 Mar 2007 12:02:54 -0400 Message-ID: <4607EEC0.1010206@syr.edu> Date: Mon, 26 Mar 2007 12:03:12 -0400 From: Steven Rowe User-Agent: Mail/News 1.5.0.4-GroupWise-IMAP-fix (Windows/20060619) MIME-Version: 1.0 To: java-user@lucene.apache.org Subject: Re: Virtually merge two indexes? References: <6e3ae6310703260858y43014848w95b9d65f6ea80ce2@mail.gmail.com> In-Reply-To: <6e3ae6310703260858y43014848w95b9d65f6ea80ce2@mail.gmail.com> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I think ParallelReader, first released in Lucene-Java 1.9, should meet your needs: ----- An IndexReader which reads multiple, parallel indexes. Each index added must have the same number of documents, but typically each contains different fields. Each document contains the union of the fields of all documents with the same document number. When searching, matches for a query term are from the first index added that has the field. This is useful, e.g., with collections that have large fields which change rarely and small fields that change more frequently. The smaller fields may be re-indexed in a new index and both indexes may be searched together. Warning: It is up to you to make sure all indexes are created and modified the same way. For example, if you add documents to one index, you need to add the same documents in the same order to the other indexes. Failure to do so will result in undefined behavior. ----- Steve Chris Lu wrote: > Hi, Gurus, > > One thing I want to do is: one index has fields like [primary-key, > not-so-frequently-updated-fields, large-content-fields,...], and > another index has [primary-key, frequently-updated-fields]. The > purpose is to make the indexing process faster by keeping large/stale > fields in one index and small/frequently updated fields in another, > linked via primary-key field. > > If I do so, is it possible to keep the index search the same? Parallel > index reader may not cut it because it works only for different > Documents into different indexes. What I want is the same Document > spread on different indexes. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org