Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
From: Paul Elschot <paul.elschot@xs4all.nl>
To: java-user@lucene.apache.org
Subject: Re: mutiple index question
Date: Fri, 20 May 2005 14:11:10 +0200
User-Agent: KMail/1.5.4
References: <A955EA1F8FE31749AEC8C998082F6C7C41A79F@hai01.hippo.local>
In-Reply-To: <A955EA1F8FE31749AEC8C998082F6C7C41A79F@hai01.hippo.local>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200505201411.10554.paul.elschot@xs4all.nl>

On Friday 20 May 2005 13:58, Max Pfingsthorn wrote:
> Hi!
> 
> I was wondering if Lucene has any sort of functionality to distribute 
indices so that different fields are stored in separate indices but they 
still refer to the same document. This would be great for a situation where 
there are many large documents which have frequently changing properties. 
Content and properties could be indexed separately. Even different sets of 
properties could be combined in maybe different MultiSearcher instances to 
speed up querying...
> 
> Any ideas on this?

Lucene doesn't have this, so you'll have to split your docs over two different
Lucene indexes and adapt the search accordingly. Cached filtering helps a
lot, but setting up a filter can still be costly.

Regards,
Paul Elschot


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org