Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@www.apache.org Received: (qmail 41339 invoked from network); 5 Jan 2005 09:58:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 5 Jan 2005 09:58:36 -0000 Received: (qmail 19082 invoked by uid 500); 5 Jan 2005 09:57:56 -0000 Delivered-To: apmail-jakarta-lucene-user-archive@jakarta.apache.org Received: (qmail 19055 invoked by uid 500); 5 Jan 2005 09:57:56 -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 19040 invoked by uid 99); 5 Jan 2005 09:57:55 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from Unknown (HELO ehatchersolutions.com) (69.55.225.129) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 05 Jan 2005 01:57:50 -0800 Received: by ehatchersolutions.com (Postfix, from userid 504) id 31C5513E200A; Wed, 5 Jan 2005 04:57:45 -0500 (EST) Received: from [192.168.1.100] (va-chrvlle-cad1-bdgrp1-4b-b-169.chvlva.adelphia.net [68.169.41.169]) by ehatchersolutions.com (Postfix) with ESMTP id DCD7513E2008 for ; Wed, 5 Jan 2005 04:57:38 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <24CFCE44DCB015489FB96D38BDF4FCAA0710D0@gerard.anchormen.nl> References: <24CFCE44DCB015489FB96D38BDF4FCAA0710D0@gerard.anchormen.nl> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <3A03B663-5F00-11D9-B175-000393A564E6@ehatchersolutions.com> Content-Transfer-Encoding: 7bit From: Erik Hatcher Subject: Re: searching while indexing. Date: Wed, 5 Jan 2005 04:57:36 -0500 To: "Lucene Users List" X-Mailer: Apple Mail (2.619) X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on javelina X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00, RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.0.1 X-Spam-Level: X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N There are no problems searching while indexing. How are you experiencing otherwise? What error do you get? Erik On Jan 5, 2005, at 4:47 AM, Peter Veentjer - Anchor Men wrote: > What is the best way to implement: searching while indexing. > > I have read the mailinglist for a while but haven`t got a good answer > to > my question. > > It is not allowed to index, while searching. But I don`t understand > why. > All the segments are immutable, so after I have created a Reader it > could use all the segments that are available at the moment. The reader > maintains references to those segments, and if the reader is not needed > anymore (or the writer says: I`m finished creating new indices... you > should can search through a newer set of segments) the reader could > delete all the old segments. The writer can create new segments based > on > the immutable-old ones and based on the new documents. After it has > created a new set, it can signal the reader to use the newer segments. > > So why is the above scenario not possible? Why are segments immutable? > And what is the best way to add documents to a (big index >20 gig) > without copying the index, and without blocking the search? > > > > > Met vriendelijke groet, > > Peter Veentjer > Anchor Men Interactive Solutions - duidelijk in zakelijke > internetoplossingen > > Praediniussingel 41 > 9711 AE Groningen > > T: 050-3115222 > F: 050-5891696 > E: p.veentjer@anchormen.nl > I : www.anchormen.nl > > --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-user-help@jakarta.apache.org