Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 52525 invoked from network); 31 May 2006 03:58:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 May 2006 03:58:50 -0000 Received: (qmail 42901 invoked by uid 500); 31 May 2006 03:58:45 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 42858 invoked by uid 500); 31 May 2006 03:58:44 -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 42847 invoked by uid 99); 31 May 2006 03:58:44 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 May 2006 20:58:44 -0700 X-ASF-Spam-Status: No, hits=2.3 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_WHOIS,FORGED_YAHOO_RCVD X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [206.190.38.242] (HELO web50309.mail.yahoo.com) (206.190.38.242) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 30 May 2006 20:58:44 -0700 Received: (qmail 50162 invoked by uid 60001); 31 May 2006 03:58:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=jLd837ftpHAxtd8FPICEaCSzDSOyiWb68Oucw8EmO8HWgFVgUCTQGNhdnSjiv4+gPn9RW9OTkqMIslbxmGrARQs/zGjSOdq0cCds+BiPLGIsgr2KCXH361mTM0sVTPqvLPhW76mK0AHU4S7SItsUC0tnmUWShig0eFfgiFNz7hM= ; Message-ID: <20060531035819.50160.qmail@web50309.mail.yahoo.com> Date: Tue, 30 May 2006 20:58:19 -0700 (PDT) From: Otis Gospodnetic Reply-To: Otis Gospodnetic Subject: Re: merge factor and real time indexing To: java-user@lucene.apache.org In-Reply-To: <359a92830605301652hea9c411ra8e15929b009af72@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Erick, Otis: What are the rules for reading an index that's being modified? Here's the sequence that I'm unclear about. open reader0 open writer add document 1 ***at this point, am I right that document1 is not visible to reader0? OG: correct. close reader0 open reader1 ***Now, is document 1 visible to reader1? Even though the writer is still open? OG: I believe reader1 will see document1 if it has been flushed to disk (i.e. is not in that in-memory buffer whose size is controlled via maxBufferedDocs). Where I'm going with this is wondering whether John needs to close/open the writer except very rarely but still be able to pick up modifications from a newly opened reader. OG: I think so. As long as he doesn't need to delete any documents, of course. Which, of course, leads to the question where his performance needs to be. It may be real-time, but how close is "close enough" to real-time? FWIW Erick Thanks Erick OG: Otis --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org