From lucene-user-return-7348-apmail-jakarta-lucene-user-archive=jakarta.apache.org@jakarta.apache.org Wed Mar 03 08:02:48 2004 Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@www.apache.org Received: (qmail 28487 invoked from network); 3 Mar 2004 08:02:48 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Mar 2004 08:02:48 -0000 Received: (qmail 53749 invoked by uid 500); 3 Mar 2004 08:02:19 -0000 Delivered-To: apmail-jakarta-lucene-user-archive@jakarta.apache.org Received: (qmail 53728 invoked by uid 500); 3 Mar 2004 08:02:18 -0000 Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Users List" Reply-To: "Lucene Users List" Delivered-To: mailing list lucene-user@jakarta.apache.org Received: (qmail 53712 invoked from network); 3 Mar 2004 08:02:18 -0000 Received: from unknown (HELO mail.tanto-xipolis.de) (213.61.178.42) by daedalus.apache.org with SMTP; 3 Mar 2004 08:02:18 -0000 Received: from tucholsky.office.tanto.de (morus.xipolis.net [10.0.1.4]) by mail.tanto-xipolis.de (Postfix on SuSE Linux 7.3 (i386)) with ESMTP id 27B5A19B719 for ; Wed, 3 Mar 2004 09:02:30 +0100 (CET) Received: from tucholsky.office.tanto.de (morus@tucholsky [127.0.0.1]) by tucholsky.office.tanto.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i2382UlT010604 for ; Wed, 3 Mar 2004 09:02:30 +0100 Received: (from morus@localhost) by tucholsky.office.tanto.de (8.12.3/8.12.3/Debian-6.6) id i2382Tid010600; Wed, 3 Mar 2004 09:02:29 +0100 From: Morus Walter MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16453.37141.866008.379348@tanto-xipolis.de> Date: Wed, 3 Mar 2004 09:02:29 +0100 To: "Lucene Users List" Subject: Re: Best Practices for indexing in Web application In-Reply-To: <40458FDD.2080508@infoworks.at> References: <2004321267.823458@kelvin> <4045063C.6040307@infoworks.at> <16453.35946.787787.616831@tanto-xipolis.de> <40458FDD.2080508@infoworks.at> X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Michael Steiger writes: > > > > Depends on your application, but if you can, it's better to keep IndexSearcher > > open until the index changes. > > Otherwise you will have to open all the index files for each search. > > Good tip. So I have to synchronize (logically) my search routine with > any updates and if the index changes I have to close the Searcher and > reopen it. > Right. The hard part is, that you shouldn't close the searcher when there still is access the that searcher. E.g. if you have a szenario - do search - index changes - access search results you cannot close the searcher until you accessed all search results. But that can be done by a little bit of reference counting. Morus --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-user-help@jakarta.apache.org