Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of spring@gmx.eu designates
 213.165.64.20 as permitted sender)
From: <spring@gmx.eu>
To: <java-user@lucene.apache.org>
References: <3241C6045C914BC486B1283E6C9D5577@msrvcn04>
 <CC1A713F-C527-46E6-8F72-926C851D3737@mikemccandless.com>
Subject: RE: IndexWriter: setRAMBufferSizeMB
Date: Fri, 8 Feb 2008 20:44:51 +0100
Message-ID: <90CCAC5AF2684E1DA3F6710317E2F421@msrvcn04>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <CC1A713F-C527-46E6-8F72-926C851D3737@mikemccandless.com>
Thread-Index: AchqgS5K8pxrPCyhQDer03+Sk8ezGwACDAkA

OK, so there is nothing in 2.3 besides IndexWriter.close to ensure that the
docs are written to disk and that the index will survive an application /
machine death? 

> -----Original Message-----
> From: Michael McCandless [mailto:lucene@mikemccandless.com] 
> Sent: Freitag, 8. Februar 2008 19:34
> To: java-user@lucene.apache.org
> Subject: Re: IndexWriter: setRAMBufferSizeMB
> 
> Well ... every time the RAM buffer is full, a new segment is flushed
> to the Directory, but that is not necessarily a "commit" in that
> an IndexReader would see the new segment, nor, that the segment would
> survive if the machine suddenly crashed.
> 
> You should't rely on when specifically IndexWriter makes its changes
> visible to readers.  The best way to be sure is to close the writer.
> 
> There is work underway now, in this issue:
> 
>    https://issues.apache.org/jira/browse/LUCENE-1044
> 
> that will add an explicit "commit" call, which you would use to 1)
> make the changes visible to readers, and 2) sync the index such that
> if the machine crashed (after commit returns) then your changes as of
> the commit will survive.  But it's not committed yet ... it will be in
> 2.4.
> 
> One way for a reader to check if a new commit has happened is to
> call the isCurrent method.  Maybe that helps?
> 
> Mike
> 
> <spring@gmx.eu> wrote:
> 
> > Hi,
> >
> > if I understand this property correctly every time the ram buffer  
> > is full it
> > gets automaticaly written to disk. Something like a commit in a  
> > database.
> > Thus if my application dies, all docs in the buffer get lost. Right?
> >
> > If so, is there any event/callback etc. which informs my  
> > application that
> > such a commit happend?
> >
> > Thank you.
> >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: java-user-help@lucene.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
> 


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